Rhino Common vs. VB.NET Legacy

I am using:

Rhino 4 (SR9)

GH version 0.8.0004

Forgive me for my lack of technical language...I am learning...

From my understanding, the primary difference between the two scripting components in Grasshopper is the language:

VB (LEGACY) is using the Open-nurbs Library

VB is using the Rhino Common Libarary

With that said, and please correct my ignorance and/or falsehood, should I be using one language over the other given the following considerations?

1. Will I have issues using VB LEGACY componenets with future releases of Rhino/GH

2. Will either language benefit/restrict my ability to generate future assemblies?

3. Are either libraries incomplete, or inaccessible? For example, it seems I am currently unable to access Rhino.Geometry.BrepFaceList.ExtractFaces

4. The grasshopper primer uses examples in legacy. Will there be an appended version with Common?

Any help is appreciated.

Replies to This Discussion

Permalink Reply by Steve Baer on February 20, 2012 at 10:23am

Hi Matthew,

If you are starting a project, I would recommend focusing on RhinoCommon. This SDK "should" be easier to use (or at least more consistent with other .NET SDKs) and is the SDK that we are updating when requests come in for new features.

If you run into something that you feel is missing from the SDK, please let us know and we'll see what we can do about adding it. Something else to consider is that you can always fall back to the older Rhino.NET SDK (legacy) even while using RhinoCommon if there is something that you absolutely need before we can get an update put together.

Thanks,

-Steve

RSS