Microsoft recently announced a roadmap for ASP.NET Core 2.2 putting the dates and things planned for the ASP.NET Core 2.2. The first preview will be out in August 2018 and RTM should be out before the end of the 2018. This release is not a major release compare to 2.0 and 2.1. This release will have a large tail of bug fixes, performance improvements, small features, and community PRs. This post provides a brief summary of what’s coming in ASP.NET Core 2.2.
What’s coming in ASP.NET Core 2.2
Below is a compiled list of what’s coming in ASP.NET Core 2.2.
- Improvement to ApiController attribute:
- ASP.NET Core 2.1 introduced the
ApiControllerattribute to denote a web API controller class which performs automatic model validation and automatically responds with a 400 error. In 2.2, the attribute will be expanded to provide metadata for API Explorer and provide a better end-to-end API documentation experience for Swagger/OpenAPI definition. - The intention is to make it possible for all MVC Core applications to have a good Swagger/OpenAPI definition by default. To achieve this, a set of analyzers will be introduced to find cases where code doesn’t match the conventions. Once found, you can either fix or opt out of conventions.
- ASP.NET Core 2.1 introduced the
- A new routing system: In 2.2, a new routing system, tentatively called Dispatcher is introduced. This is designed to run the URL matching step very early in the pipeline so that the middleware can see the Endpoint that was selected as well as metadata that is associated with that endpoint.
- With ASP.NET Core 2.2, Microsoft offers an OpenID Connect based authorization server, which will allow your ASP.NET application to act as an authentication point for your projects, be they web site to the API, SPA to API, native application to an API or, for distributed applications API to API.
- Today there are no tools built into Visual Studio or the dotnet CLI to help you execute HTTP verbs against your API. In 2.2, the “dotnet” CLI tool will allow to test HTTP requests with any HTTP verbs.
- A new code generator tool to produce client side code (C# & TypeScript) for calling and using the WEB APIs.
- HTTP/2 support in Kestrel & HttpClient.
- Inbuilt plan for health check.
- SignalR to support for Java or C++.
- With ASP.NET Core 2.2, you should be able to run ASP.NET Core applications in-process in IIS, giving a significant performance boost.
For more details, you can read this post. ASP.NET Core 2.2 should be exciting with these small new features, much better performance and faster experience.
Thank you for reading. Keep visiting this blog and share this in your network. Please put your thoughts and feedback in the comments section.
