Ah indeed. With _GrasshopperDeveloperSettings Memory Load option enabled and the load mechanism set to Plugin Default, the plugin doesn’t win. That’s clearly a bug.
I wonder if this ever got solved? I think I see the same: I define the assembly attribute
but Grasshopper only loads direct if the option is switched off in the developer settings. Before digging deeper, let me know if this problem has been solved or not. Thx!
It’s a new problem, somehow Mono.Cecil fails to parse the assembly. Could simply be because I’m using an old version of Cecil which doesn’t know how to handle newer .NET version assemblies.
I think I fixed the problem and if I’m right the next Rhino WIP will again properly respond to assembly load demands.
If not, please send me the GHA so I can test it over here.