December ? came out
ASP.NET Core ???r3r36. It is included in the delivery of .NET Core 2.2. About .NET Core 2.2 i I wrote recently and now you need to open the topic in depth. Let's see what's new for us.
 
from the usual place and use 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 3r330. .NET Core
, ASP.NET Core and Entity Framework Core up to version ???. The new version of the SDK is ???. The following requirements for the Visual Studio version are:
 
3r361  
3r3117. Visual Studio version ??? and above
 
3r3117. Visual Studio for Mac version 7.7 and above 3r3-33120.  
3r3117. Visual Studio Code C # extension version ??? and higher
 
3r3122.
 
Visual Studio ??? Preview ? which was also posted on December ? allows you to optionally connect the .NET Core SDK ???.
 
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 have already written about these features in previous releases, and accordingly you can read the detailed description of the links: 3r-3252.
 
3r361  
3r3117. Improved integration with popular Open API libraries (Swagger), including checks at the stage of writing code using special 3r3r5757 code analyzers.
 
3r3117.
Endpoint Routing adds a 20% routing speed for MVC 3r-3-3577.
 
3r3117. Improved url generation with class 3r3204. LinkGenerator and
Support Parameter Transformer route (and post by Scott Hanselman 3r3-33257. In addition) 3r3-33120.  
3r3117.
New Health Checks API to monitor the health of the application 3-333257.
 
3r3117. 3r3108. Up to 400% performance improvement on IIS, due to hosting within a single process 3r32577.
 
3r3117.
Improved performance validation MVC models up to 15% 3r33257.
 
3r3117. 3r3108. Support for Problem Details (RFC 7807) in MVC, which allows you to get detailed error results in API 3r-3257.
 
3r3117.
A preliminary version of the HTTP /2 server in ASP.NET Core
 
3r3117. 3r3108. Update templates for Bootstrap 4 and Angular 6
 
3r3117. 3r3113. Java client for ASP.NET Core SignalR
 
3r3117. 3r3118. Up to 60% of the HTTP Client performance on Linux, and up to 20% on Windows 3r33257.
 
3r3122.
 
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
 
Project BeatPulse 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, their support in BeatPulse is great. Here is what BeatPulse itself writes about the new Health Checks API: 3r-3252.
 
“BeatPulse is a community-developed project designed to provide mechanisms for testing the functionality of applications, networks and a wide range of various services that are often found in the enterprise, for example, 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 3r3142 repository. AspNetCore.Diagnostics.HealthChecks
. 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. ”
 
3r3147. What's next
 
After the announcement of plans for ASP.NET Core 2.? several features were published that are not listed above, including the API for authorization through IdentityServer? 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 ???r3r3240.
 
To migrate an ASP.NET Core project from 2.1 to 2.? open the csproj file of the corresponding project, and change the value of 3r3204. TargetFramework on 3r3204. netcoreapp???r3r3223. . 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) should not indicate the version of the 3r3204 package. Microsoft.AspNetCore.App Because this link is managed by the SDK itself automatically. If you still do this, you will receive a warning when building.
 
More information about the upgrade to ASP.NET Core ???r3r3174.
.
 
3r3179. Support life cycle
 
ASP.NET Core 2.2 is the latest release in the “Current” release train. 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 201? otherwise they risk being left without support.
 
More information about the policies support. NET Core .
 
3r3193. 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 up your project so that it uses the existing version of ANCM, this is done by setting the property 3r3204. AspNetCoreModule the values ​​“ AspNetCoreModule ”, for example:
 

netcoreapp???r3r3214.
enable 64-bit option in Azure Portal , and the entire site will start to 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 3r-3234. in a separate article 3r33257. .
 
Feedback
 
As always, please do not hesitate to leave feedback in the form of shshui on https://github.com/aspnet/AspNetCore . It is important!
 
Translator's Note
: and in the comments on Habré, too, would be nice to write something. It is important!
 
Don't forget that DotNext tickets are going up from January 1st. Personal - for a thousand, and Standard - for two thousand. Details about Early Bird - on site .