Rhino 9 BETA - Developer Links

Rhino Developer
1

Rhino Developers: See the links below for details on how to write or update your plugins for the Rhino 9 BETA.

Post a comment in this thread if you have questions or are looking for something more.

  • RhinoCommon, the the cross-platform .NET SDK for Rhino, is available for the Rhino 9 BETA as a NuGet package.
  • Note: NET 10 is now the official platform, and the .NET Framework has been deprecated. See the migration guide for details.
  • Rhino 9 is binary compatible with the previous written C++ plugins. However, there are new features to explore in the updated Rhino 9 C++ SDK. Download it here!

Sincerely,
Mary Ann Fugier

3

Hey i asked here as there seems to be conflicting information posted in this thread :smiley:

Should the target be .net 10 (as stated here and other places) or .net 8 as said in this thread by @dale ?

4

The documentation is ahead of the NuGet package, isn’t it?:rofl:

image
image1183×586 39.5 KB

image
image893×499 20.1 KB

5

Thanks @mary

Early testing is showing Rhino 9 & .net 10 to be 10% faster than Rhino 8 & .net 7 for our plugin :slight_smile:

Upgrade process so far as been seemless.

6

@mary @will is it safe to release a yak package targetting the Rhino 9 Beta? or is it too early?

If so what Distribution Tag should I use so that the package version doesn’t get picked up by Rhino 8 and below? I imagine it would be rh9_any or rh9_1?

When I target RhinoCommon 9.0.26167.11545-wip with .net 10 and use Rhino 9 WIP’s yak.exe i get a Distribution Tag of any which i fear would be picked up and auto-installed by Rhino 8 users who have auto-update on. My colleagues in support may have something to say if that happened!

Is it too early to release yak packages for Rhino 9 Beta?

7

You’ll want to make sure that your package has rh9 (or rh9_0) in the distribution tag part of the filename – e.g. “example-1.0.0-rh9-any.yak”.

I’ll look into why this didn’t happen automatically (YAK-368).