Hi,
we developed a Rhino + GH plug-in.
It should be used within Rhino7 and Rhino 8.
For Rhino 8 we had to update it from .NET Framework 4.8 to .NET 7.
Now we are unsure how to publish it properly via the package manager.
The YAK file based on .NET 7 shouldn’t be shown in the Rhino 7 package manager.
The YAK file based on .NET Framework 4.8 should not be shown in the Rhino 8 package manager.
Currently both YAK files show up in both programs.
Is there a solution for this scenario? As far I can tell, it can’t be solved by the name of the YAK file. Please correct me if I am mistaken.
Thank you for answer(s) in advance!
1 Like
Have a look at Rhino - The Anatomy of a Package (rhino3d.com)
“[…] Unless the app is any , an app version must be included in the form <major>_<minor> . The minor version is optional and is useful if a plug-in relies on an SDK change made in a service release. The platform can be win , mac or any (i.e. cross-platform). […]”
Did you try this already?
Hi,
sure, we did try, but it doesn’t restrict you from the listing in newer version. How it could?
we are in a similar position, I use -rh8-win.yak at the end of the package filename this hides it from Rhino 7 as far as i know
I have not found any way to specify that a Rhino 7 package is not compatible with Rhino 8
I think Rhino assume that all 7 packages will automagically run on 8.
Thanks for the reply.
As my colleague Jaroslav Kopecky wrote - we tried it already.
As far I can tell it should solve the situation: “YAK based on .NET7 shouldn’t be shown in Rhino 7”.
But the other scenario: “YAK file is based on .NET Framework 4.8 shouldn’t be shown in Rhino 8” is still open.
I was thinking that more developers may run into that issue. So thanks for adding your comment David.
1 Like