Does Rhino6 Grasshopper has a dll hell?

[Nguyen_Minh_Chau]

I encountered this problem a few months ago. Please see this thread. My post is at the end

Error: Could not load file or assembly

No. Ideally you wouldn’t use COFF loading. You probably have the checkbox in the _GrasshopperDeveloperSettings command enabled. That shouldn’t be the case. You can add an assembly attribute to your plugin informing Grasshopper how you want to load your plugin (I can’t give you an example now, on an iPad). Or you can handle the framework assembly resolver event and load your pdf dll through code.

Basically, I could not call out my recently created custom object even when I already load in the most recently built dll.

I came across this article about dll hell in Revit. Wonder if Rhino6 and grasshopper has a similar issue

dll hell is real

[DavidRutten]

There can be issues with dll references going wrong. You may compile your plugin against a newer version of RhinoCommon or Grasshopper than your user may have, which would then result in load-failure. You may reference a non-standard dll such as Kangaroo or MeshMachine which may then conflict with other plugins referencing and distributing other versions of those assemblies. Finally there may be versioning issues between Rhino5, Rhino6 and RhinoWip releases.