If you fail to install this then Visual Studio for Mac won't be able to find any of your simulators. After that you should be good to go to properly start running and debugging iOS apps! #DEVEXPRESS XAMARIN INSTALL# Who would have thought that Android Emulators would be a headache!?!?!! Rosetta 2 is amazing, but when it comes to the default Android Emulator it falls over because it can not run Kernel extensions and doesn't support VMs that are doing x86_64 virtualization. #DEVEXPRESS XAMARIN ANDROID#ĭo not fear though because Google has actually been working on fixing this and has a special native ARM64 build of the Android Emulator! They have been building it out on GitHub and it is now included in the Android Studio AVD manager, however it isn't available just yet in the Visual Studio for Mac AVD manager :(. A workaround for now is that you can just download and run it manually from their GitHub releases page! I downloaded Preview 3 and installed it into the Applications folder. To launch the emulator you will need to hold down the control button and then double click launch it the first time. When you launch it you will get a warning that adb could not be located and must manually be assigned. This location can be set manually in the. You can find this in VSM -> Preferences -> SDK Locations -> Android: Turn off the 'Use detected ADB location' and then browse for adb manually that Visual Studio for Mac uses. The actual path of adb will be /Users/YOUR_USER_NAME/Library/Developer/Xamarin/android-sdk-macosx/platform-tools/adb. After you locate this, you will be good to go! It will show up now when you run the emulator (I pinned it) under the name :). Now, most of the tools here are all going through Rosetta 2, but I have to say that overall it feel pretty fast. I picked up the MacBook Air and not the Pro and I can create a new project and get up and running on a simulator in under 1 minute, which is pretty great: More to come!Īs an early adopter I know things aren't going to be perfect, but things are looking pretty good after playing around for a few hours. I need some more time to setup my entire environment and tools to get a real feel for things. I haven't experimented with every workload yet, but most of the traditional ASP.NET Core, and Blazor Server things seem to work well from my testing so far. Blazor WebAssembly seems to have a few issues, but that feel like something that will get worked out soon. If you have an M1 and find any issues with Visual Studio for Mac please report a problem on the Developer Community.

Xamarin devexpress