Library dependencies trying to load into Dynamo from Package

[archinate]

Hello all, I am trying to prepare a package which depends on providing several libraries (dlls) in addition to a Dynamo zero touch library. I am noticing that Dynamo attempts to load any library that is included in the package. In my case, things seem to load correctly... but it seems this could have unintended consequences in other circumstances.

Here is a screenshot of dependencies attempting to load into Dynamo... these should not be loaded into Dynamo at all and are referenced by another library.

In my case, my "Rhynamo" tool ships with the following... only "CASE_Rhynamo.dll" should get loaded by Dynamo. The others are reference.

• "CASE_Rhynamo.dll" (this is the zero touch library that exposes new nodes... this is the only library that should be loaded)
• "CASE_RhinoConnection.dll" (a custom library referenced by Rhynamo)
• "Rhino3dmIO.dll" (the OpenNURBS library referenced by Rhynamo)
• "rhino3dmio_native.dll" (the C++ library referenced by OpenNURBS)

I should note that Grasshopper defines a special extension for dll libraries that get loaded as plug-ins. For example, a dll with a "gha" extension would get loaded into Grasshopper, whereas other dlls provided as dependencies are not loaded.

[mjkkirschner]

@tatlin @pboyer

[mjkkirschner]

I believe this pull request which was merged handles the issue:, if so, we may need some better documentation and UI hinting around this

https://github.com/DynamoDS/Dynamo/pull/2896

[pboyer]

@archinate That PR does solve your problem. You will need to declare which dll's are "node libraries" when submitting your package. This is done by simply right clicking on the assemblies in the Publish Package dialog. Please re-open if this is not your problem.