GH Component was build against a newer minor version

grasshopper
rhinocommon-v6
rhino6

#1

Hi everybody,

I have coded a GH Component and it is working fine in my computer. The problem is that in some others I get
gh
even if Rhino is fully updated.
How do I solve this problem?

Thanks


(jesterKing) #2

6.9 is still in release candidate stage, not a full service release just yet. That hopefully happens in the coming 24-48 hours or so (unless something dramatic is found). Until the 6.8 is the latetst available service release.

While working on plug-ins it is generally advisable to stay with the oldest possible release to build against. Obviously if something crucial to your plug-in gets fixed in a newer SR you should update. It just means that that then will be the new minimum requirement for your plug-in.


#3

I understand… so how can I get the older GH extensions for VS2017?


(Giulio Piacentino) #4

The comment by @jesterking was meant for the developers of the Mindesk plug-in. You can download the Service Release Candidate if you want to use SR9 now. The option is in the Updates and Statistics tab under _Options.

Thanks,

Giulio


Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com


#6

Ok thanks! after the update it works.

However, just to feel safer, is it possible to get somewhere an older version of the Grasshopper SDK? (I have downloaded the extension for VS2017)


(Giulio Piacentino) #7

You can swap the reference from the Grasshopper.dll you use to the one on Nuget:

Thanks,

Giulio


Giulio Piacentino
for Robert McNeel & Associates
giulio@mcneel.com


#8

Giulio,

thanks for your reply! However it seems that it has been updated even on nuget. Is there another way to get an older version?

Gennaro


(Giulio Piacentino) #9

@gennaro, I am sorry for the late reply. I do not know how to help… exactly, what type of error are you getting? Nuget is something @will has more knowledge than me about.


(Will Pearson) #12

Hey @gennaro, all versions are available for the Grasshopper nuget package. You can specify the version of the package that you wish to install in Visual Studio. See this StackOverflow answer for more details. It’s always good to reference an earlier version if possible for the very reason that you’ve experienced (unless of course you rely on functionality or bug fixes only available in a later release).


#14

Thanks!! it seems working!