Where .NET Core 2.1 is Headed

| by Jeff Martin Follow 16 Followers on Feb 15, 2018. Estimated reading time: 1 minute |

Microsoft's Scott Hunter has presented the roadmap for what Microsoft expects to include in the release of .NET Core 2.1. Hunter announced that Microsoft is able to observe active usage of approximately 500k developers daily. The usage of .NET Core 2 surpassed .NET Core 1.X in September 2017 according to Microsoft's telemetry.

With that successful launch in hand, Microsoft is focusing on a few themes for .NET Core 2.1: faster build performance, faster internal engineering system, and improved compatibility with the .NET Framework. All .NET Core project should have faster build times in 2.1, with larger projects showing large gains according to Microsoft’s preliminary benchmarks.

.NET Core 2.1 will debut an approach to framework compatibility called "minor-version roll-forward". This reduces the need to match an application to its runtime. This means an application targeting Core 2.1 can run without modification on future minor versions (2.2, 2.3, etc.).

Ready to run (R2R) precompiled assemblies are being slated for reductions in their install size. The approach taken in .NET Core 2 lends itself to faster startup times, but provides minimal benefit once the assembly is running. Since most customers usually launch an application and let it run, a fast startup time is of minimal value versus a reduction in storage space.

The command-line tooling supporting .NET Core is also slated for improvement. For greater developer convenience, several new commands will be included in .NET Core 2.1 to support the packaging and installation of developer tools. The command dotnet pack will package up assemblies for distribution while dotnet install tool exampleApp will install it to a user's .dotnet\tools folder. This location will be automatically added to the path so it is then possible to make use of the new executable regardless of the local directory.

Joining these additions is an improvement for self-contained apps to correctly be packaged with the dotnet publish command. In 2.1, the resulting package will include the latest patched runtime by default.

While a formal schedule has not been released, Hunter says his team is anticipating a preview release of .NET Core 2.1 to be made public in February. A second preview will be released in March, with a release candidate slated for April. At some point in the first half of 2018, the formal release-to-manufacturing build will be released.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you