Hope this helps, let me know if it’s not clear.

dll (so if a new version of the 3rd party components is released, we do have to manually repeat that step). We simply reference a copy of the 3rd party gha file with the extension renamed to. So the only references to the third party components are in the second project with the static class.īecause grasshopper has loaded the third party dll at startup, and ours only at the time any solving is called, it doesn’t matter if we built against a slightly different version etc. and I lost the license in the grasshopper for the caramba, and when starting version 6 of the rhinoceros or when starting version 7, there is no border. installed the latest version of rhino 7 and karamba 1.33. gha, and in the components solve method we call methods on a static class in the second project. with rhino 6 everything was fine, I decided to switch to rhino 7 in parallel without deleting version 6. One that is only essential code to define components (ie inputs, outputs, icons etc) and a second dll that has the references to the third party components. Our solution has two projects (ie 2 dlls). with rhino 6 everything was fine, I decided to switch to rhino 7 in parallel without deleting version 6. When grasshopper is loading assemblies for components, it won’t necessarily load all dependencies at that time.

See if this helps understand what worked for the Geometry Gym plugins.

Karamba grasshopper crack