Latest Update Causes Development Issues for VS2022

I have been working on a plugin for a while using VS2022 and Net7.0. Most recently, I updated Rhino to version 8.17.+. While in VS2022, I start Rhino in debug mode. The plugin is registered fine. However, then I attempt to run the command, nothing happens. Debugging shows that the RunCommand(RhinoDoc doc, RunMode mode) method is never called.

I decided to start fresh and delete the plugin from Rhino using Regedit and then, with a newly opened Rhino outside of VS2022, drag and dropped the .rhp file to install it again. This did not change the result.

I then cleared the current plugin using Regedit, and dragged in an older version the plugin of a different name. Nothing happens when running the command. However, looking at Tool > Options > Plugins I see that the old version is enabled, but not loaded. So, I loaded the old plugin, and attempted to run it. Nothing. However, I took note of the GUID for the old plugin.

Following that, for the fun of it, I dragged in the current plugin, outside of VS2022. Then, I looked at the Plugins list, and saw that the new version was listed, loaded and enabled. Interestingly, the GUID was the same as the old plugin of a different name. Ok, then, I entered the command name of the current version and the new plugin ran.


Sadly, when I closed Rhino, and opened it again, the new plugin command did nothing. When I fired up VS2022, and tried to debug Rhino with the new plugin and RunCommand(…) is not invoked.

I hope this long explanation is helpful to figure the cause(s) of not being able to run my plugin. Happy to forward the .rhp and .dll file if needed.

Thanks ahead of time.

I have confirmed that Rhino version 8.13.24317.13001 is working with VS2022 in a manner that addresses my issues described above. For Rhino versions above 8.13, I cannot comment. Luckily, I have this older version on another personal computer. Dave

After more thorough research, the reason my plugin did not display its Main window was not from the lastest Rhino update. Rather, the precipitating event was rolling back to a previous version from my GitHub repository. ( I am quite new using Git and Github.) Rolling back to a prior version from Github, does not preserve the supporting libraries used by my plugin’s WPF windows and controls. Once I replaced all the required .dll’s in the same directory as the plugin .rhp file, all was fine. Apologies for crying foul. My mistake entirely. Dave.

1 Like