Today, we are announcing .NET Core 2.1 Preview 2. The release is now ready for broad testing, as we get closer to a final build within the next two to three months. We’d appreciate any feedback that you have.
You can download and get started with .NET Core 2.1 Preview 2, on Windows, macOS, and Linux:
You can see complete details of the release in the .NET Core 2.1 Preview 2 release notes. Known issues and workarounds are included in the releases notes.
You can develop .NET Core 2.1 apps with Visual Studio 2017 15.7 Preview 1 or later, or Visual Studio Code. We expect that Visual Studio for Mac support will be added by .NET Core 2.1 RTM.
Thank you very much! We couldn’t have gotten to this spot without you, and we’ll continue to need your help as we work together towards .NET Core 2.1 RTM.
Build-time performance is greatly improved in .NET Core 2.1, particularly for incremental builds. These improvements apply to both
dotnet build on the command line and to builds in Visual Studio. We’ve made improvements in the CLI and in MSBuild in order to make the tools deliver a much faster experience.
The following image shows the improvements that we’ve made since .NET Core 2.0. We have focused on large projects.
These improvements are from many changes including the following ones:
We’re happy to look at your project if you don’t see significant improvements from using .NET Core 2.1 Preview 2.
We added long-running servers to the .NET Core SDK to improve the performance of common development operations. The servers are just additional processes that run for longer than a single
dotnet build invocation. Some of these are ports from the .NET Framework and others are new.
The following SDK build servers have been added:
- MSBuild worker processes
- Razor server
The primary benefit of these servers is that they skip the need to JIT compile large blocks of code on every
dotnet build invocation. They auto-terminate after a period of time.
You can manually terminate the build server processes via the following command:
dotnet buildserver shutdown
This command can be used in CI scripts in order to terminate worker processes after builds are completed. You can also run builds with
dotnet build -nodeReuse:false to prevent MSBuild worker processes from being created.
The following tools have been added to the SDK:
We found that these tools were so popular that having to add them to individual projects didn’t seem like the right design, so we made them part of the SDK.
These tools were previously DotNetCliToolReference tools. They are no longer delivered that way. You can delete the
DotNetCliToolReference entries in your project file when you adopt .NET Core 2.1.
.NET Core now has a new deployment and extensibility story for tools. This new experience is inspired by npm global tools
With Preview 2, the syntax for global tools has changed, as you can see in the following example:
dotnet tool install -g dotnetsay dotnetsay
You can try out .NET Core Global Tools for yourself (after you’ve installed .NET Core 2.1 Preview 2) with a sample tool called dotnetsay.
All tools operations now use the
dotnet tool command. The following new functionality has been added in Preview 2:
dotnet tool install— installs a tool
dotnet tool update— uninstalls and reinstalls a tool, effectively updating it
dotnet tool uninstall— uninstalls a tool
dotnet tool list— lists currently installed tools
--tool-path— specifies a specific location to (un)install and list tools, per invocation
.NET Core Applications, starting with 2.0, roll forward to minor versions. You can learn more about that behavior in the .NET Core 2.1 Preview 1 post.
However, .NET Core has the opposite behavior for previews. Applications, including global tools, do not roll forward from one preview to another or from preview to RTM. This means that you need to publish new versions of Global Tools to support later previews and for RTM.
The policy for previews is a bit controversial. The premise behind it is that we may make breaking changes between a given preview and the final RTM build. This policy enables us to do that while minimizing breakage in the ecosystem. There is also the likely case that software built for previews was not tested with RTM builds, however, this rationale is less compelling.
This policy has been in place since the start of the .NET Core project. Global Tools makes it a bit more challenging. We’d appreciate your feedback and insight on it.
We made major improvements to sockets in .NET Core 2.1. Sockets are the basis of both outgoing and incoming networking communication. The higher-level networking APIs in .NET Core 2.1, including HttpClient and Kestrel, are now based on .NET sockets. In earlier versions, these higher-level APIs were based on native networking implementations.
SocketsHttpHandler is now the default implementation for HttpClient. The biggest win of SocketsHttpHandler is performance. It is a lot faster than the existing implementation. There are other benefits, such as:
- Elimination of platform dependencies on libcurl (for Linux and the macOS) and WinHTTP (for Windows) – simplifying both development, deployment, and servicing.
- Consistent behavior across platforms and platform/dependency versions.
You can use one of the following mechanisms to configure a process to use the older
From code, use the
The AppContext switch can also be set by config file.
The same can be achieved via the environment variable
DOTNET_SYSTEM_NET_HTTP_USESOCKETSHTTPHANDLER. To opt out, set the value to either false or 0.
On Windows, you can choose to use
SocketsHttpHandler on a call-by-call basis. To do that, instantiate one of those types and then pass it to HttpClient when you instantiate it.
On Linux and macOS, you can only configure HttpClient on a process-basis. On Linux, you need to deploy libcurl yourself if you want to use the old HttpClient implementation. If you have .NET Core 2.0 working on your machine, then libcurl is already installed.
dotnet publish now publishes self-contained applications with a serviced runtime version. When you publish a self-contained application with the new SDK, your application will include the latest serviced runtime version known by that SDK. When you upgrade to the latest SDK, you’ll publish with the latest .NET Core runtime version. This applies for .NET Core 1.0 runtimes and later.
Self-contained publishing relies on runtime versions on NuGet.org. You do not need to have the serviced runtime on your machine.
Using the .NET Core 2.0 SDK, self-contained applications are published with .NET Core 2.0.0 Runtime unless a different version is specified via the
RuntimeFrameworkVersion property. With this new behavior, you’ll no longer need to set this property to select a higher runtime version for self-contained application. The easiest approach going forward is to always publish with the latest SDK.
We are consolidating the set of Docker Hub repositories that we use for .NET Core and ASP.NET Core. We will use microsoft/dotnet as our only .NET Core repository going forward.
The publicly available statistics suggest that most users are already using the dotnet repo, as you can see via the following docker pull badges:
You can learn more about this change and how to adapt at aspnet/announcements #298.
We also added a set of environment variables to .NET Core docker images, for 2.0 and later. These environment variables enable more scenarios to work without additional configuration, such as developing ASP.NET Core applications in a container.
- To Linux
- To Windows
Note: These environment variables will be added to the 2.0 images later this month.
The biggest additions are supporting Ubuntu 18.04 and adding official ARM32 support.
We will support the following operating system versions for .NET Core 2.1:
- Windows Client: 7, 8.1, 10 (1607+)
- Windows Server: 2008 R2 SP1+
- macOS: 10.12+
- RHEL: 7+
- Fedora: 26+
- openSUSE: 42.3+
- Debian: 8+
- Ubuntu: 14.04+
- SLES: 12+
Alpine support is still in preview.
We will support the following chip architectures:
- On Windows: x64 and x86
- On Linux: x64 and ARM32
- On macOS: x64
ASP.NET Core 2.1 Previews will not be automatically deployed to Azure App Service. Instead, you can opt in to using .NET Core previews with just a little bit of configuration. See Using ASP.NET Core Previews on Azure App Service for more information.
Visual Studio Team Service support for .NET Core 2.1 will come closer to RTM.
There are some key improvements that are important to recap from Preview 1. For more details, take a look at the .NET Core 2.1 Preview 1 Announcement.
- Minor-version roll-forward
- Span<T> and Memory<T> and friends
- Windows Compatibility Pack
Please test your existing applications with .NET Core 2.1 Preview 2. Thanks in advance for trying it out. We need your feedback to take these new features across the finish line for the final 2.1 release.
.NET Core 2.1 is a big step forward from .NET Core 2.0. We hope that you find multiple improvements that make you want to upgrade.
Once again, thanks to everyone that contributed to the release. We appreciate all of the issues and PRs that you’ve contributed that have helped make this preview release available.