If the steps above were followed, this previous path can be safely removed. This is most likely: C:\Users\\AppData\Local\Xamarin\Universal\AndroidSDK. There will be another Android SDK installed. Note: If Xamarin was previously installed via the Visual Studio or the Xamarin Universal Installer. Visual Studio will need to be restarted for this to take effect. The location of the Java SDK should be set here too. There is a setting for both the path to the NDK and SDK previously installed. Set up the SDK paths within Visual Studio. At the time of writing this there isn’t a direct link to cycle 9, so download cycle 8 and update it. Download the individual installation package per platform (and not the universal installer). Alternatively if you don’t have it, you can manually install it. To upgrade to Cycle 9 use the Updater Channel within Visual Studio. If you installed Xamarin with Visual Studio 2015, you have it already. This will simplify the later setup if done now. Xamarin does not require this, but Android Studio will later request it be installed. Install “Sources for Android SDK” for API 25. Install API 25 SDK Platform (and whichever other APIs you require) Install Android SDK platform tools 25.0.3 C:\AndroidSDK\tools_r25.2.3-windowsįrom command line execute \tools\android This will open the SDK manager. Extract the contents to a location that’s easily accessible. This is just a zip file not requiring any installation. The simplest and cleanest is to install the command line version of the SDK Extract this to a location that’s easily accessible: C:\AndroidSDK\android-ndk-r13b-windows-x86_64 Install Java JDK 1.8 圆4 (Use the latest update of this available) This guide is specifically aimed for Windows and Visual Studio 2015+ users. I also find it’s much cleaner to install everything manually without the installers. I put together a guide to make the new Xamarin Cycle 9 release and Android Studio 2.2.3 run together without any pain and also without wasting disk space with multiple copies of Android Sdks.
I run the two side by side often especially when I am binding native libraries for Xamarin. This may be needed if you are an Android developer experimenting with Xamarin or maybe you are migrating an Android application to Xamarin. You may need to run Android Studio and Xamarin side by side from time to time.
0 kommentar(er)
