I’m glad I found this discourse thread as we have been having some issues with Rhino 6 plugins automatically loading in Rhino 7 and creating instability and crashing in v7. I wanted to chime in on this issue as I’ve observed this to be a persistent and recurring problem being encountered by Rhino 7 users and this has impacted our plugins as well as other plugins out there.
It seems an odd decision that Rhino 7 would automatically load plugins originally deployed/registered for a Rhino 6 install. I understand that a “continuity of experience” for those upgrading to 7 could be theoretically beneficial, but it also seems to be a problematic assumption that a Rhino 6 plugin is designed to “just work” in Rhino 7.
The developer code above is helpful, but it seems that there should be something more fundamental - I would expect there to be a setting or some other deliberate user decision needed to migrate or prevent migration of plugins from 6 to 7.
cc @stevebaer @dale @will