We are having an issue with a Visual Studio for Mac Extension build. Currently we have dependancies to MonoDevelop.Ide and MonoDevelop.Core and we have hardcoded version(17.0) the problem is that for example if Visual Studio for Mac 2022 Preview release new version17.2 our extensions stops working bacause it cannot find the dependancy with the correct version. So is there a way to build an Extension that would work in more than one Visual Studio for Mac 2022 release or we have to release new version of the Extension each time Visual Studio for MAC 2022 releases a new version?
Excuse me if this question is not for this group, just did not find specific group for VS for Mac.
Previously we were trying to migrate our VS for Mac extensions to VS for Mac 2022 so we kinda succseeded by following the steps from this wiki https://github.com/mhutch/MonoDevelop.AddinMaker/wiki/Migrating-AddInMaker-projects-to-support-Visual-Studio-2022-for-Mac-v17.x But one of our extensions uses gtk-sharp to show some custom dialogs within Visual Studio and this functionality is failing runtime after the migration with this error (System.TypeInitializationException: "The type initializer for 'Gtk.DialogAttribute' threw an exception." ---> System.DllNotFoundException: "Unable to load shared library 'libgtk-win32-2.0-0.dll' or one of its dependencies). This is working within VS for Mac 2019.
Any help on this would be greatly appreciated.
Hello again @mrward another question I have regarding Visual Studio for Mac 2022. So we have custom project templates that we install in VIsual Studio and they work fine and all excep the part when we try to open specific project template through a command in the menu in that case we it seems that the method we use to open the specific template fails and fallbacks to the latest used template. This is the line we use(that by the way was working fine in VS for Mac 2019): IdeApp.ProjectOperations.NewSolution("TemplateID", false);
The templates are visible in the VS new project wizard and are working correctly. So the issue should be just with line above.
So is there something that is changed in VS for Mac 2022 and is there a place we can track such changes to the extensibility model of VS for Mac.
Thank you in advance.