Is there some way, then, that something could be tweaked to make this work? Any thoughts or suggestions are welcome. I've considered resigning to using NAT and port forwarding the API but would rather not as other projects are already dialed in to use Bridged setup, where the Mac and Windows have their own addresses on same network. I also tried instead using SSL tunneling through the bridged interface and the app deployed but this setup also seemed to cause high CPU usage in Visual Studio (not seen if tunneling to a standard emulator). If you are regular users looking forward to using Android Emulator for Mac to run Android Games and Simple Android Apps then you can try Droid4x, or Bluestacks, which will the best choice out there. I connected Wireshark and saw a bunch of retransmissions, indicating some kind of network problem - maybe with Virtual Box? Xamarin is developer-friendly and is more or less leaned towards developers and coders.

I've tried connecting the Windows guest directly to the Player's special 'host-only' network (using a second virtual adapter) which adb seemed to connect fine to until I actually tried to deploy and. Go to Project Settings > Player > Android Tab > Publishing Settings. I can do 'Bridged' networking no problem with iOS development. Visual Studio Visual Studio for Mac Normally, all three Xamarin. I've seen the helpful guides for accessing the Xamarin Android Player in Visual Studio that's on a virtual guest (in my case, Virtual Box)Īnd they work fine - except the solution's requirement to set the guest's network mode to 'Shared' (NAT in Virtual Box parlance) means my deployed app does not reach a test API residing on the windows guest.