However, Visual Studio shows the option to start debugging as disabled:
The plugin project has been created on Windows, and works perfectly fine there. Are there some Mac-specific settings that should be changed in the csproj file?
Hmmmmm, I’d only be speculating without being able to see the .csproj file. Have you tried creating a boiler-plate “test” project from the RhinoCommon Visual Studio extension templates to see if you can debug that way? (When I do that here, I’m able to debug and hit breakpoints.) If you are able to, we’d need to figure out what is different between the contents of the .csproj (looking at the xml source) files themselves.
I ended up digging into Rhino’s Visual Studio for Mac extension. Its code for detecting the McNeelProjectType doesn’t work in our case, due to the nesting level of .csproj files. I solved the problem by adding a RhinoPluginType property to my .csproj files.