Visual Studio Emulator for Android first experience, emulatorandroid
Visual Studio Emulator for Android has been released for a while, but it has never been used. After downloading and installing it two days ago, the overall experience is much better than that of Google's built-in simulator. Visual Studio Emulator for Android follows the excellent tradition of windows phone simulators, And the smoothness is similar to that of a real machine.
The following are some installation and usage records
1. Enable Hyper-V before installation. This is the same as that of the windows phone 8 simulator. First, check whether the computer supports Hyper-V. If it is an intel CPU, it must be at least i3. In addition, it should be noted that some computers support Hyper-V, but it is not enabled by default in BIOS, which requires you to first open the BIOS before you can. Then select Hyper-V in "enable or disable windows" on the control panel, and restart the computer.
2. Official Website address https://www.visualstudio.com/en-us/msft-android-emulator-vs.aspx
Download vs_emulatorsetup.exe is still fast.
3. After installation, open the simulator management interface. below is
Two 4.4-version simulators are installed by default. The other simulators can be used only after they are downloaded. I have downloaded a 4.2 Nexus S, and the download speed is quite fast. From the drop-down box in the upper left corner, we can see that the current maximum API Level of the simulator is 23, and the lowest API Level is 17, which is generally enough for development.
4. If there is a green triangle, It is downloaded. Click the simulator to start it. The startup process takes about 1 minute. The following is what is started:
Click ">" in the control bar on the right to open the additional tool, as shown below:
We can see that there are 7 functions in the additional tool. Here we have tested the function, which is quite useful.
5. Below I wrote a demo in adt-bundle to run it in this simulator. It turns out that ADB cannot find this simulator. Why? The answer is https://msdn.microsoft.com/en-us/library/mt228282.aspx?adb. It turns out that the Microsoft Android simulator needs to know the folder path of the Android SDK on the local machine. After knowing this path, it can find ADB and tell ADB that it has been started and can be used. How to set the path here? You need to set in the registry, open the registry, find the HKEY_LOCAL_MACHINE \ SOFTWARE \ Wow6432Node \ Android SDK Tools Folder in the directory tree on the left, and find the key named Path under this folder, modify the value to the path of the Android SDK folder on your local machine. If the registry does not contain the Android SDK Tools Folder or the Path key, create a new one.
6. some bugs are found during the use process. For example, if the problem occurs in the Chinese Input Method, you can enable the system to bring the Google Pinyin input method. If you slide on the screen, the system will automatically start the input method and continuously output "c ", as follows:
Write this for the time being. If you have any questions about the usage in the future, try again. :)