RhinoCommon with native DLLs

[stevebaer]

Here’s some related posts that you may find helpful

.NET C++ Bridge Code

Continuing the discussion from Hyphenated commands: I used to write scripts to automatically generate “bridge” code, but it always ended up (putting it kindly) not very good to work with. I now write the code by hand. It is much easier to write .NET code to access C++ than C++ code accessing .NET so I would recommend always going in that direction if at all possible. Much of RhinoCommon is written as a thin layer of C# that accesses C++ code through pinvoke. You can see how this is done by …

.Net interface for C++ plugin

Hi, I would like to add a .Net interface for all our C++ plugins (EvoluteTools), allowing the functionality to be used from Rhino.Python, Grasshopper, etc. Most of the functionality can already be accessed from RhinoScript. Is there a particularly clever way of doing this, minimizing the amount of redundant code? Would you have a hint for me where to start reading? Kind regards, Alex