Hi,
I’m developing for Rhino 7 and noticed the latest version of RhinoCommon 7 is 7.37 in nuget, but 7.38 is the latest available download version of Rhino. Is there a reason for this?
As far as I know there were no API/SDK changes, so you can just keep on using the 7.37 nuget package.
OK, good to know. This is medical software and we need to be really careful about making sure the users use the exact version of Rhino that matches the DLL that that plugin was built on. For this reason, we have a check in the software that verifies that the running version of Rhino is exactly the right build number that matches what is expected.
What gets most complicated for us is that the McNeel website, as far as I know, does not allow you to download specific versions of the software, so new users would be downloading the most recent Rhino 7, which would result in a flag in the software about a version mismatch.
Is there some way we can get a link to the specific Rhino build so that users always install the correct version? Alternatively, if we could get the latest DLL in nuget it would perhaps be even simpler.
You should be able to keep building against say Rhino 7.36 package. Newer versions of the same major version should be able to load plug-ins build against versions of an older service release version (unless there was a SDK-breaking change, which should happen never).
So if you want your users to be able to user say Rhino 7.35 than you should have a nuget package that is not newer than that.
If you build against 7.38 you force your users to update to that. 7.37 nuget package allows your users still to stay on 7.37 if that is useful. There should be no need for your users to have a plug-in that is built against exact same nuget package version.
Other than that we’ll have to ask @will about the published nuget package versions (or @fraguada).
2 Likes
I gave the build system a nudge. We should have 7.38 nuget packages out there now, if they’re needed.
1 Like
Thanks!
Actually, are there any plans to provide links to specific Rhino builds for download (even private links that you provide to specific users)? I realize that newer versions of Rhino should work with plugins built on older versions of the API, but in-practice, we need a very controlled system and our users are all in-house. The plugin is not going to be publicly distributed and we will have very specific protocols for people downloading a specific matching version of Rhino. If we have people on multiple versions of Rhino it becomes an issue of needing to validate every version of our plugin against every version of Rhino someone might have installed.
This has historically created some complexities for us since the McNeel website only provides access to the latest Rhino installer.
Direct download links to 7.38 sent via private message!
Thanks!