Backwards compatibility with service releases

Is there a way to control which service releases my rhino plugin is compatible with? I’ve recently created a plugin and when distributing an alpha version of it a couple users noted that Rhino forced them to download and upgrade to the latest service release (not just the latest release of Rhino) in order to use the plugin. I would like to be able to fix this so that anyone with Rhino V5 can run the plugin regardless of his/her service release version.

Hi Bailey,

RhinoCommon plug-ins will load in the same version, or newer, of Rhino that they were built against. For example, if you have Rhino 5 SR 9, then a plug-in you build will load in Rhino 5 SR9, SR10, etc., but not in SR8.

The same holds true for plug-ins built with the Rhino C++ SDK, which has service release versions equal to that of Rhino.

Does this help?

– Dale

Hi Dale,

Thank you for the prompt reply. This is very helpful!