Rhino_DotNET will be discontinued

Edit: this is no longer true. Rhino_DotNET will still be available in Rhino6 albeit in a somewhat reduced form. It will probably disappear in Rhino7. Once we have a webpage up explaining what, how and why, I'll post a link to it here.

Come Rhino6, the old Rhino_DotNet SDK will no longer be available. This means the Legacy VB/C# components will no longer work, nor will any GHA files that depend on that SDK. It'll be pure RhinoCommon all the way.

If you are still using Rhino_DotNet.dll, please stop doing so asap. If you need functionality which isn't yet available in RhinoCommon, let us know and we'll make sure it gets added.

David Rutten

david@mcneel.com

Tirol, Austria

Replies to This Discussion

Permalink Reply by huaxiamengqing on September 3, 2013 at 6:11pm

When Rhino6 is released?

Permalink Reply by David Rutten on September 4, 2013 at 2:59am

No idea when it will be released. The first beta is probably a few months away.

David Rutten

david@mcneel.com

Tirol, Austria

Permalink Reply by huaxiamengqing on September 4, 2013 at 6:02pm

dying for it!

Permalink Reply by michael sprinzl on September 16, 2013 at 8:53am

Oh this also means some nice hidden classes will be gone forever? like the RMA.UI.MRhinoUiDockBar ...

will be a alternative for this?

Permalink Reply by David Rutten on September 16, 2013 at 12:24pm

There will be. The UI for Rhino6 will be .NET based and I think Steve and John just about removed the last traces of Rhino_DotNET from the UI code.

David Rutten

david@mcneel.com

Tirol, Austria

Permalink Reply by Paul N Jeffries on October 7, 2013 at 5:44am

So this means that if we want our existing DotNet plugins/components to work in Rhino 6 they will need to be re-written to use RhinoCommon?

As somebody with over 100,000 lines of Rhino_DotNet-dependent code that this will affect I can't say I'm entirely enthusiastic about this.

Permalink Reply by David Rutten on October 7, 2013 at 6:04am

Unfortunately yes.

David Rutten

david@mcneel.com

Tirol, Austria

Permalink Reply by Paul N Jeffries on October 8, 2013 at 4:20am

That's... unfortunate. The old "so don't worry about a wasted development effort" line that I see has been recently removed from the RhinoCommon page was a bit of a fib, then? It should really have read "so don't worry about a wasted development effort... until Rhino 6; then worry about it lots".

To help me decide how high a window I should jump out of; when you say 'no longer available' what exactly do you mean? Presumably anything that interacts directly with Rhino itself is out but will the basic OpenNURBS/Rhino geometry objects still be usable, or as they're wrapping the C++ SDK will they be FUBAR'd as well? Will the existing conversion utilities in RhinoCommon be maintained?

Could we, for example, use RhinoCommon to get geometry out of Rhino/Grasshopper, convert it to On_/MRhino_ objects, do whatever we need to do to it with our old code and then convert it back to RhinoCommon form to go back into Rhino itself?

Permalink Reply by Steve Baer on October 9, 2013 at 12:56pm

Hi Paul,

We're going to have a meeting about this issue next week while David is in the Seattle office.

-Steve

Permalink Reply by Jon Mirtschin on October 10, 2013 at 2:35am

Hi Steve,

Is there any early builds of v6 Rhino common? I'd like to start testing early, I don't think my github issues about drag'n'drop and building your own brep were ever closed (not to say I've tested service release builds to see if they were addressed).

These were 2 issues preventing me from removing the rhino dotnet references from my plugin for v5. Would be good to check if any others as early as possible.

I think .rui interaction (adding tabs etc) was another request I would have. Probably this discussion should be on discourse or github.

Cheers,

Jon

Permalink Reply by Paul N Jeffries on October 10, 2013 at 3:46am

Thanks Steve, let me know how it goes!

Permalink Reply by Paul N Jeffries on October 23, 2013 at 2:57am

Hi Steve,

Any update on the outcomes of this meeting?

Cheers,

Paul