by Curtis Wensley (Last updated: Tuesday, April 16, 2024)

Rhino 8 now uses the open source .NET Core Runtime for running .NET code on both Windows and Mac. This brings some performance improvements and aligns the .NET runtimes used across platforms. Previously, Rhino 7 and earlier used the mono runtime on Mac, and .NET Framework exclusively on Windows.

On Windows, you can still optionally run using the .NET Framework runtime in the case of compatibility issues or running inside other software that requires it (e.g. Rhino.Inside Revit).

Most plugins are already compatible when running in .NET Core without any recompilation, but in the case of any incompatibilities you may need to update your plugin.

Advantages of .NET Core for Rhino

Using .NET Core allows Rhino and plugins to take advantage of many performance improvements which will make just about all .NET code execute much faster. This can potentially provide huge productivity gains with computational libraries or large data sets.

Additionally, using .NET Core on Mac eliminates a lot of compatibility issues between the Mac and Windows versions of Rhino making it easier to make plugins work on both platforms.

Choosing the .NET Runtime on Windows

There may be reasons to continue to use .NET Framework on Windows, in particular if you need to use 3rd party plugins that aren’t compatible with .NET Core yet. The disadvantage to using .NET Framework is that Rhino may run a little slower in certain use cases. There are two ways to select the runtime that Rhino uses:

1. Use the SetDotNetRuntime command, then restart Rhino.
2. Pass either /netcore or /netfx as an argument when launching Rhino.exe. This overrides the SetDotNetRuntime setting.

Rhino.Inside

When using Rhino.Inside, the runtime Rhino uses is the same as the host application. For example, since Revit currently uses .NET Framework, Rhino.Inside.Revit will also run using .NET Framework. Custom Rhino.Inside applications should still work, however migrating to .NET 7+ would allow you to take advantage of the performance improvements offered with .NET Core.

Checking if your plugin is compatible

Rhino 8 will automatically scan plugins for any known API breakages when running in .NET Core, and will provide a report of the specific assemblies and APIs that are not comatible.

To check manually, you can use the compat.exe tool on each of your plugin assemblies:

You can also use Microsoft’s upgrade assistant to analyze your project for compatibility issues.

Migrating your plugin

It is recommended to keep your plugin(s) targetted at .NET 4.8 so that it can run in either runtime on Windows. Most plugins won’t need any changes to run in Rhino 8.

For Mac-specific plugins you can target .NET 7 as that is the only runtime available in Rhino 8. If you want the plugin to be compatible with Rhino 7, keep the target at .NET 4.8.

If your plugin uses any unavailable or non-working APIs when running in .NET Core, some code changes may be necessary. The compat report will show you which APIs you need to avoid.

If you multi-target your project to both .NET 4.8 and .NET 7.0, you can find compatibility issues during compilation. Keep in mind you should only distribute the .NET 4.8 version on Windows.

Debugging .NET Core on Windows

To debug in .NET Core on Windows you will need to use Visual Studio 2022 or Visual Studio Code.

Visual Studio determines the debugging runtime by the project’s target framework, so either you need to multi-target your project, or create a separate launcher project used for debugging purposes only.

With Visual Studio Code, use the coreclr debugger type from the C# extension. You do not need to multi-target or create a launcher project when using Visual Studio Code.

How to add a .NET Core launcher project in Visual Studio

This is only required when you want to debug in .NET Core using Visual Studio 2022 on Windows.

1. Right-click on your solution node and select Add > New Project…
2. Select the C# Console App then click Next.
3. Enter a name e.g. Rhino8Launcher then click Next.
4. Select .NET 7.0 for the Framework then click Create.
5. Right-click the launcher project and select Properties.
6. Go to the Application > General panel and change the Output Type drop down to Windows Application.
7. Go to the Debug > General panel and click Open debug launch profiles UI.
8. Delete the default profile by clicking the Delete selected profile button.
9. Create a new Executable profile, and enter the path to Rhino.exe. E.g. C:\Program Files\Rhino 8\System\Rhino.exe

You may also want to add your plugin project as a dependency of the launcher project so it compiles before launching.

Debugging on Mac

On Mac, get the latest RhinoCommon Visual Studio extension for Visual Studio for Mac. The extension automatically selects which version to debug based on the referenced version of RhinoCommon.

To override this, you can go to the Project Properties > Rhino panel and select the launcher version. This adds a <RhinoMacLauncher>8</RhinoMacLauncher> property to your project file.

You can also use Visual Studio Code with the coreclr debugger type from the C# extension. Set the program to /Applications/Rhino 8.app/Contents/MacOS/Rhinoceros and set either the RHINO_PLUGIN_PATH or GRASSHOPPER_PLUGINS to the path of your built plugin/component.

Discussions

Jump over to our developer discourse channel to ask questions regarding the move to .NET Core.

Edit this page

Edit on GitHub

History

Admin