So yeah as the article explains we just have to update the registry entry with the accurate path to the Android SDK installation in our system, so that Visual Studio can start up ADB to connect to the Emulator.
This seem to be happening by default with fresh installations of VS lately, where as the Android SDK installation path in the above registry entry doesn’t seem to be matching with the actual SDK installation location in our system, which is probably done by default when installing Visual Studio 2015. This is very well explained in this Visual Studio troubleshoot article:
This is due a wrong registry entry in the system, where as Visual Studio is looking to start up the ADB and connect to it, in order to connect to the Emulator, but due to this wrong registry entry, VS is unable to find the path to ADB, to start it up. The cause for this is Visual Studio debugger was unable to connect to the started Emulator through the ADB (Android Debug Bridge).
I was having a already built solution and up and running Emulator, but the VS couldn’t connect to the Emulator. You must keep in mind that my project was building fine, and the Emulator also started running successfully and booted up itself. So let me post the solution for you right here. So after Googling a while I figured out the problem thanks to wasting a bunch on hours on google search and forums, since many others were also having the same issue. Specifically the build log was on a hang state after “Emulator is already running” step, as I saw in the output log in VS. The project was successfully building itself, and the Visual Studio Android Emulator also started running successfully, but then the build process was on a hang state after the Emulator started running. So few days back after doing a fresh installation on my WIndows 10 laptop, and installing Visual Studio, I tried running a Xamarin Forms project, with the Visual Studio Android Emulator.
0 kommentar(er)
