I’m trying to find the most painless way to deploy Rhino 8 within our office. For now we want to continue running it with .NET Framework. Has anyone found a way to set the dot net runtime in registry, not just for the current user but in local machine so that anyone who logs in will run in .NET framework?
Rhino - .NET Core vs .NET Framework (rhino3d.com)
We’ve looked at all of these, but we will run into issues if someone else logs in to the same machine
What need requires you to run Rhino 8 in .net framework @Alexis3?
It’s mainly driven by the plugins we use. We feel it’s more stable right now.
I concur with @Alexis3
At least in the AEC industry, I think live links and interoperability plugins such as Tekla Live Link and Rhino.Inside Revit still necessitate .NET Framework. I wish it didn’t, but I would suspect this is reality for some time. It wouldn’t surprise me if there were more plugins in different fields with the same problem.
With these constraints, we have also faced problems with not all the essential plugins running correctly in the .NET Framework mode of Rhino 8. Mainly Lunchbox and Karamba3D have suffered from this at least in the past and I think Lunchbox also even still. It cripples how scripts and tools are used, since you can run into this problem depending on whether the user is having .NET Core or Framework enabled. It can vary and then nothing works robustly. And there are no easy to understand error messages, like: “Hey, it seems you tried opening a script in Grasshopper that depends on Lunchbox. However, you are running Rhino in a mode that cannot handle Lunchbox or vice versa, thus nothing works.”
The plugins you use do work in net core but are less stable?
@Alexis3 I ask because I don’t think there is (currently) a solution, and before we figure out what can be done I’d love to make sure its necessary. And also stability issues are something good to know about.
For sure, some day it’ll be all net core which will be lovely
At least Revit 2025 is netcore, and Rhino.Inside.Revit supports it