1. Introduction to the version of Xamarin for VS
Here is a brief introduction to the release of Xamarin for VS:
...Earlier versions (omitted)
Published in November 2015: Xamarin for VS 4.0.0.1717 Stable version (charged)
Release in March 2016: Xamarin for VS 4.0.1.145 Stable (charged)
Release in May 2016: Xamarin for VS 4.0.4.4 Stable (Enterprise Edition, Free)
Release in June 2016: Xamarin for VS 4.1.0.530 Stable (Enterprise Edition, Free)
Notice:
Since Microsoft officially acquired Xamarin in February 2016 and built Xamarin into VS2015 Update2 (after Xamarin was acquired by Microsoft, Xamarin for VS has become all free and open source since May 2016), the Xamarin for VS 4.1.0.530 released in June 2016 no longer needs to be cracked, nor does it require a separate account, and it is directly installed or upgraded to be the enterprise version. 2. Install Xamarin for Visual Studio 4.1.0.530 Stable version
Here is the interface when installing Xamarin for Visual Studio 4.1.0.530:
If VS2015 has not been installed yet, download VS2015 with Update2 and install it directly.
If you have installed VS2015 and Update2, run VS2015, [Tools]->[Options]->[Xamarin], and then select [Upgrade].
Below is the screenshot of the interface you saw after installing Xamarin for VS 4.1.0.530 and running VS2015:
3. Install the 32-bit version of JDK-8u60 (for Windows)
It is highly recommended to install the following Java JDK version after upgrading Xamarin for VS:
After installation, run VS2015, [Tools]->[Options]->[Xamarin], and modify the configuration:
4. Upgrade Android SDK
Below is a screenshot after the upgrade of the version, and the emulator version has also been upgraded:
5. Recreate a new version of the emulator
If there is a problem running the original program after upgrading, the most thorough solution is to delete the original created emulator first and then rebuild the new version of the emulator.
Here is a new emulator created after upgrading the Android SDK:
6. Pay attention to the version selection of the .NET framework when creating a new Android project
Special reminder: Since Xamarin for VS 4.1.0.560 has changed a lot, in addition to supporting the development of the latest Android version, performance and stability have also been greatly improved compared with earlier versions. Therefore, when building a new Android project after upgrading, you must choose .NET Framework 4.6.0 or 4.6.1, otherwise the design interface of the .axml file in the project cannot be displayed. 7. Upgrade Chapter 3 The SDK of Baidu Map application is version 3.7.3
This time, the Baidu Map SDK application written in C# has also been upgraded to use the 3.7.3 version released by Baidu in May 2016. Baidu Voice Synthesis (tts) has also been upgraded to use version 2.2.6 released by Baidu in May 2016.
The upgraded solution screenshot is as follows:
Notice:After upgrading, you need to modify the SHA1 value in the account you applied for on Baidu. The new version of SHA1 is not the same as the original version of SHA1. If you do not modify it, a verification error will be displayed when running the Baidu Map application example in Chapter 3.
After upgrading according to the above steps, the screenshot of the recreated MyDemos run is as follows:
8. Problems with Visual Studio Emulator for Android under Win10
Although Microsoft's own Hyper-V virtual machine under Win10 has very powerful functions and is very convenient to use, the Android emulator provided by Visual Studio Emulator for Android, which is started with a Hyper-V virtual machine, is faster to start than Google's emulator and is simple to configure, but there are several problems that cannot be solved, so in the end, I had no choice but to give up Hyper-V.
The problem with the Android emulator provided by Visual Studio Emulator for Android is:
(1) After the map layer of Baidu Map is displayed, the zoom function is also normal and runs rapidly. However, no matter how hard it is, it only displays the map layer, but does not display the text layer in the map. However, the same solution and the same code show up normally in the emulator provided by Google.
(2) There are many models of Android emulators provided by Google, such as there is no simulator that provides Android watches, and no simulator that provides Android N version. In addition, it is also impossible to manually modify the configuration of the emulator.
(3) Hyper-V and HAXM conflict, you can only choose one of the two and cannot be used at the same time.
Taking into account the above factors, it is currently more convenient for INTEL's CPU to use the Android emulator provided by Google and the HAXM GPU accelerator. When the computer is expanded to 8GB of memory, the running speed is also fast, the upgrade is simple, the configuration is flexible, and it is also very convenient to use.
For ARM CPU, when the computer is expanded to 8GB of memory, the Android emulator provided by Google is still fast.
However, if the display problem of Baidu maps is not considered or the problem of only displaying maps without displaying map text annotations and meeting the memory requirements of at least 8GB, the Android emulator provided by Visual Studio Emulator for Android, which is started with a Hyper-V virtual machine under Win10 is still very convenient (fast speed, the emulator can also access the Internet directly), and it is also very easy to install and run iOS and Linux systems with a virtual machine.
The above is all the content of this article. I hope it will be helpful to everyone's study and I hope everyone will support me more.