On December 4, ASP.NET Core 2.2 was released , it is included in the delivery of .NET Core 2.2. I wrote about .NET Core 2.2 quite recently and now I need to open the topic in depth. Let's see what's new for us.

Where to get

The .NET Core SDK (2.2.100) can be downloaded from the usual place and used both on your development machine and servers. New Windows Server hosting, runtime installers and binary archives for updating servers are available there.

This release is dedicated to updating .NET Core , ASP.NET Core and Entity Framework Core to version 2.2.0. The new version of the SDK is 2.2.100. The following requirements for the Visual Studio version are:

• Visual Studio version 2017 15.9 and higher
• Visual Studio for Mac version 7.7 and higher
• Visual Studio Code C # extension version 1.17.1 and higher

Visual Studio 2019 16.0 Preview 1, which was also posted on December 4, allows you to optionally connect the .NET Core SDK 2.2.100.

What's new

The main idea behind this release of ASP.NET Core is to improve developer productivity and platform functionality with a special focus on the Web / HTTP API. As always, we took care of the performance. We already wrote about these features in previous releases, and accordingly you can read the detailed description of the links:

• Improved integration with popular Open API libraries (Swagger), including checks at the stage of writing code using special code analyzers
• Endpoint Routing adds 20% routing speed for MVC
• Improved URL generation using the LinkGenerator class and support for the Parameter Transformer route (and the post by Scott Hanselman in addition)
• New Health Checks API for monitoring application health
• Up to 400% performance improvement on IIS, due to hosting within one process
• Improving MVC model validation performance up to 15%
• Support for Problem Details (RFC 7807) in MVC, allowing you to get detailed error results in the API
• Preview version of HTTP / 2 server in ASP.NET Core
• Updating templates for Bootstrap 4 and Angular 6
• Java client for ASP.NET Core SignalR
• Up to 60% of the HTTP Client performance on Linux, and up to 20% on Windows

Translator's note : all links lead to original sources in English. If you want to see something of this translated for Habr - write in the comments!

Health check integration with BeatPulse

The BeatPulse project now supports the new Health Checks API. In fact, now you can quickly and easily add checks that are compatible with many popular systems and dependencies, and their support in BeatPulse is great. Here is what BeatPulse itself writes about the new Health Checks API:

“BeatPulse is a community-developed project designed to provide mechanisms for testing the functionality of applications, the network, and a wide range of various services that are often found in the enterprise, such as SQL Server, MySQL, PostgreSQL, Redis, Kafka, and many others. When Microsoft announced ASP.NET Core Health Checks in release 2.2 roadmap, the BeatPulse team ported all existing packages and features related to such checks to the Microsoft Health Checks abstraction from the AspNetCore.Diagnostics.HealthChecks repository. In addition, the BeatPulse team added other features, such as pulse check (Application Insights and Prometheus), crash messages and a UI, in which you can adjust monitoring parameters and view a global screen with system health status. This UI is distributed as a Docker image published on the Docker Hub. ”

What's next

After the announcement of plans for ASP.NET Core 2.2, several features were published that are not listed above, including the API for authorization via IdentityServer4, client code generation for the Open API (Swagger), and the command line utility for the HTTP REPL. These features are still being developed and are not ready for release. Nevertheless, we hope to finish and publish them as addons in the coming months. Suffer a little while we bring them to a state of readiness, and thanks in advance.

How to migrate to ASP.NET Core 2.2

To migrate an ASP.NET Core project from 2.1 to 2.2, open the csproj file of the corresponding project, and change the TargetFramework value to netcoreapp2.2 . If you target the .NET Framework 4.x, you should not do this.

In the end, you will need to update the links to the NuGet packages to match the latest stable versions. It is important that projects targeting the .NET Core (as opposed to the .NET Framework) do not have to indicate the version of the Microsoft.AspNetCore.App package, since this connection is controlled automatically by the SDK itself. If you still do this, you will receive a warning when building.

More information about the upgrade to ASP.NET Core 2.2 is available here .

Support life cycle

ASP.NET Core 2.2 - the most recent release in the "Current" release trainee. This is the first release after the release of 2.1 LTS, which announces the difference between the LTS and Current trains. Train Current is the place where the newest features, improvements and regular bug fixes are applied, it is recommended for most users. Notice that both the LTS and Current receive service security updates and critical stability updates. Now we can assume that 2.2 will be the last non-service update in the lifecycle of the 2.x line, and those customers who do not want to use LTS will need to migrate to 3.0 GA within 3 months after its release in the second half of 2019, otherwise they risk being left without support.

More information about .NET Core support policies is available here .

Availability through the Azure App Service

Now the .NET Core 2.2 SDK, .NET runtime and the updated IIS module for ASP.NET Core are in the process of being deployed on the Azure App Service worldwide. We want to complete this process by the end of December 2018.

Some regions may receive an updated runtime before updating the IIS module (ANCM), which is required by default for projects targeting ASP.NET Core 2.2. In addition, it is the basic requirement for new in-process hosting. If you see startup errors after deployment to the Azure App Service, try setting your project to use the existing version of ANCM, this is done by setting the AspNetCoreModule property to " AspNetCoreModule ", for example:

 <PropertyGroup> <TargetFramework>netcoreapp2.2</TargetFramework> <AspNetCoreModuleName>AspNetCoreModule</AspNetCoreModuleName> <AspNetCoreHostingModel>OutOfProcess</AspNetCoreHostingModel> </PropertyGroup> 

As soon as the target region is updated to the latest version of ANCM, it will be possible to remove these properties everywhere and redeploy applications — as a result, you will have a fresh version of ANCM.

This release, among other things, adds support for 64-bit architecture on the Azure App Service for .NET Core. If you run your ASP.NET Core application on .NET Core 2.2 with in-process hosting enabled, you can simply enable the “64-bit” option in Azure Portal , and the entire site will run in a 64-bit process. Additional information on the operation of ASP.NET Core applications in a 64-bit process on the Azure App Service with other configurations is described in a separate article .

Feedback

As always, please, do not hesitate to leave feedback in the form of yours at https://github.com/aspnet/AspNetCore . It is important!

Translator's note : in the comments on Habré, too, would be nice to write something. It is important!

Don't forget that the DotNext tickets will go up from January 1st. Personal - for a thousand, and Standard - for two thousand. Details about Early Bird - on the site .