I’m developing a plugin that has started to have the problem summarized in the title. The infuriating thing is that it’s not consistent; one some machines, the init fails, and on others, it works fine. It works on all of our development machines, which might be a clue, but I can’t think of how. It’s such a weird problem. When I rename the .rhp to a .dll and load it in an Object Browser I can see the plugin class (with appropriate ancestry) fine. I have been able to establish that when it doesn’t work the plugin constructor isn’t being called.
It might matter that the plugin doesn’t directly inherit from Rhino.PlugIns.PlugIn; there’s an intermediate class in the way. But I that system hasn’t changed since the last time this worked.