lesnotwin.blogg.se - Visual studio 2019 change install location

(Visual Studio 2019 Preview also uses for the NDKs.) For the common case where is C:\, the following patch would suffice. The install prefixes for the AndroidNDK_*.swixproj components in the Visual Studio Installer were changed from to in February 2018. I will plan to file a follow-up issue for that problem.) Rough sketch of a possible fixĮxternal/xamarin-android-tools/src//Sdks/AndroidSdkWindows.cs already includes a list of hardcoded fallback search paths, but it turns out the entries for Visual Studio 2017 are outdated. (A separate problem is that Bundle assemblies into native code should produce the same error message as AOT Compilation rather than the confusing message about "C:\platforms".

Attempt to archive the project via Build > Archive, or attempt to create a signed APK on the command-line:Ĭ:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Xamarin\Android\(2758,3): error : Could not find a part of the path 'C:\platforms'.

In the project options, enable Android Options > Bundle assemblies into native code or Android Options > AOT Compilation (Experimental) for the Release configuration.

Create a new Android App (Xamarin) > Single View App.

For the purposes of this scenario, it doesn't matter if Visual Studio 2017 is also installed or not. NET workload and the one Optional component offered for that workload: Android SDK setup (API level 27).

Install Visual Studio Enterprise 2019 Preview with the Mobile Development with.

NET workload can rely on the Auto Install Android SDKs feature for on-demand installation of Android NDK. There are some pros and cons to consider, but maybe the Mobile development with. I will plan to file a follow-up item in Developer Community related to this. But the Android NDK is still available under Individual components and as part of the Mobile development with C++ workload.

The Visual Studio Installer no longer shows the Android NDK as an optional component associated with the Mobile development with.

One tricky remaining question is to decide how and when to help users install the NDK via the Android SDK Manager rather than via the Visual Studio Installer. The motivation behind that change is that the Android SDK Manager can now be used to fetch the NDK instead of the Visual Studio Installer, and in that case the path of the NDK will be within the Android SDK directory and won't need its own registry entry.

The Visual Studio Tools for Xamarin no longer set the AndroidNdkDirectory property of the HKCU\SOFTWARE\Xamarin\VisualStudio\*\Android registry key.

These problems stem from two changes in Visual Studio 2019 Preview: This is the first of a few follow-up bugs related to: