Skip to content

.NET 6.0 Preview 1

Pre-release
Pre-release

Choose a tag to compare

@jonathanpeppers jonathanpeppers released this 17 Feb 19:32
· 940 commits to main since this release

Downloads:

See the .NET 6 download page for the full release notes for .NET 6.0 Preview 1.

Android and iOS projects will need to add additional NuGet feeds. An example NuGet.config file would be:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <clear />
    <add key="dotnet6" value="https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet6/nuget/v3/index.json" />
    <add key="xamarin" value="https://pkgs.dev.azure.com/azure-public/vside/_packaging/xamarin-impl/nuget/v3/index.json" />
    <!-- Any additional feeds -->
  </packageSources>
</configuration>

Android

Prerequisites:

  • You will need the Android SDK installed as well as Android SDK Platform 30. One way to acquire this is to install the Xamarin workload in the Visual Studio installer. You can manage Android SDKs from Tools > Android > Android SDK Manager from within Visual Studio.

iOS

Prerequisites:

  • Xcode 12.3

Using IDEs

Currently, you can use Visual Studio 2019 16.9 Preview 4 on Windows
(with the Xamarin workload) with a few manual steps.

Open an Administrator command prompt to enable the
EnableWorkloadResolver.sentinel feature flag:

> cd "C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin\SdkResolvers\Microsoft.DotNet.MSBuildSdkResolver"
> echo > EnableWorkloadResolver.sentinel

NOTE: your path to Visual Studio may vary, depending on where you
selected to install it. Preview is the default folder for Visual
Studio Preview versions.

Restart Visual Studio after making this change.

Visual Studio for Mac support will be coming in a future release.

Known Issues

Debugging Android applications that are built for multiple architectures may crash on some devices. To workaround, try using a single architecture by defining a single RuntimeIdentifier in the .csproj file:

<PropertyGroup>
  <RuntimeIdentifier>android.21-arm64</RuntimeIdentifier>
</PropertyGroup>

Release builds should be unaffected by this issue.