This dramatically lowers the barrier to entry for developing Visual Studio Mac extensions. Therefore, there are compelling reasons to use Xamarin.Forms to build Visual Studio Mac extensions: As a bootstrapped business, this time-cost makes it prohibitively expensive to develop tools that are UI-centric. IntroductionĮver since I commercialised MFractor in June 2017, I've been pulled to the idea of using XAML and Xamarin.Forms to build user interfaces for Visual Studio Mac extensions.įor MFractor, developing tools like the Image Wizard or localisation wizard cost days to weeks of engineering effort. If you would like guidance on this, please email We provide consulting services to assist the development of Visaul Studio Mac extensions and would be happy to help. 🚨If you choose to use Xamarin.Forms to build UIs, proceed with caution 🚨Īt MFractor, we recommend using XWT or Xamarin.Mac/AppKit to build user interfaces for Visual Studio Mac. Using Xamarin.Forms inside Visual Studio Mac caused instability in both MFractor and Visual Studio Mac itself.
In the end, we decided that this technique was not commercially viable.
MFractor has removed all Xamarin.Forms user interfaces as of October 2018. Use Xamarin.Forms to build user interfaces for your Visual Studio Mac extensions.
