Announcing ASP.NET Core in .NET 7
.NET 7 is now released! ASP.NET Core in .NET 7 includes everything you need to build rich modern web UI and powerful back-end services.
What’s new?
Here’s a sampling of the great new features and improvements in ASP.NET Core for .NET 7:
- Servers and runtime
- Rating limiting: Limit the rate of handled requests using flexible endpoint configuration and policies.
- Output caching: Configure caching for responses to more efficiently handle requests.
- Request decompression: Accept requests with compressed content.
- HTTP/3: Built-in support for HTTP/3, the latest HTTP version based on the new QUIC multiplexed transport protocol.
- WebSockets over HTTP/2: Use WebSockets over HTTP/2 connections.
- WebTransport (experimental): Create streams and data grams over HTTP/3 with experimental support for WebTransport.
- Minimal APIs
- Endpoint filters: Use endpoint filters to run cross-cutting code before or after a route handler.
- Typed results: Return strongly typed results from minimal APIs.
- Route groups: Organize groups of endpoints with a common prefix
- gRPC
- JSON transcoding: Expand the reach of your gRPC services by also exposing them as JSON-based APIs
- OpenAPI with JSON transcoding (experimenal): Use experimental support for generating OpenAPI specs for your gRPC JSON transcoded services.
- gRPC health checks: Report and check the health of gRPC server apps.
- gRPC client
AddCallCredentials: Create clients that send authorized requests using bearer tokens.
- SignalR
- Client results: Return client results to the server in response to requests from the server.
- MVC
- Nullable view and page models: Nullable page and view models are now supported to improve the experience when using null state checking.
- Blazor
- Custom elements: Build standard HTML custom elements with Blazor to integrate Blazor components with any JavaScript-based app.
- Handle location changing events: Intercept location changing events to create custom user experiences when navigating.
- Bind after/get/set modifiers: Run async logic after data binding and independently control how data binding gets and sets the data.
- Dynamic authentication requests: Create dynamic authentication requests at runtime with custom parameters to handle advanced authentication scenarios in Blazor WebAssembly apps.
- Improved JavaScript interop on WebAssembly: Optimize JavaScript interop call when running on WebAssembly using the new
[JSImport]/[JSExport]support. - WebAssembly SIMD & exception handling: Improve performance with .NET WebAssembly ahead-of-time (AOT) compilation using WebAssembly SIMD and exception handling support.
For a full list of everything that’s new in ASP.NET Core in .NET 7, check out the ASP.NET Core in .NET 7 release notes.
Get started
To get started with ASP.NET Core in .NET 7, install the .NET 7 SDK. .NET 7 is also included with Visual Studio 2022. Mac users should use the latest Visual Studio 2022 for Mac preview.
Upgrade an existing project
To upgrade an existing ASP.NET Core app from .NET 6 to .NET 7, follow the steps in Migrate from ASP.NET Core 6.0 to 7.0
To upgrade an existing ASP.NET Core app from .NET 7 RC2 to .NET 7, update all ASP.NET Core package references to 7.0.0.
That’s it! You should be all set to enjoy the benefits of .NET 7.
See also the full list of breaking changes in ASP.NET Core for .NET 7.
Join us for the .NET 7 release at .NET Conf 2022
Come celebrate with us and learn all about the .NET 7 release at .NET Conf 2022, a FREE, three day virtual developer event with over 80 sessions featuring speakers from the .NET team and the broader .NET community. The conference starts TODAY and goes from November 8-10. We hope you can join us!
.NET 7 on Azure
.NET 7 is already deployed and ready to be used across your favorite Azure services, like Azure App Service, Azure Functions, and Azure Static Web Apps. Get started building with .NET 7 on Azure today!
Thank you!
Thank you to everyone in the community who helped make this release of .NET 7 possible! This release represents the culmination of many GitHub issues, pull requests, design feedback comments and documentation updates contributed by many members of the .NET community. We couldn’t have made it to this point without you!
We hope you enjoy this release of ASP.NET Core in .NET 7. We’re eager to hear about your experiences building with it. Let us know about any feedback you have on this release on GitHub.
Thanks again, and happy coding!
Light
Dark
34 comments
I ran the bits for Blazor Hybrid (.NET 7 and the latest VS 17.4) and am planning to stylise the CSS using DevTools. I press CTL+SHFT+I and DevTools opens. I can pick my way thro’ the HTML and CSS, but I can’t seem to get the tools to jump to the right place when I highlight or click on a Blazor Hybrid element in the app. Is there a way of synchronising tools with the app one it’s loaded from VS? Maybe I should be using some kind of Edge/Canary preview?
On a separate note, is MS creating a clean hybrid project template or is the idea dead?
Many thanks.
If you select the browser dev tools and type Ctrl-Shift-C you should then be able to hover over and select UI elements in the app and the dev tools will show the corresponding HTML.
Clean in what sense? Is there a GitHub issue tracking this request that you can link me to?
Hi Daniel, thank you for your very prompt response, much appreciated.
Ah, I can finally see this! Both Ctrl+Shft+I and Ctrl+Shft+C are needed, the latter key-set is acting like ‘inspect’ on Edge’s browser context menu, nice!
Apologies for the poor jargon, should have said ’empty’ rather than ‘clean’. You mentioned the potential feature in a response to my query 1st August (think that was about preview 6) as this was something you were discussing with your colleagues on GitHub: https://github.com/dotnet/maui/issues/9126 – I see there has been further discussion so maybe it’s a feature for .NET 8?
Yup, we’ll look at adding an empty .NET MAUI Blazor template for .NET 8. Please give the corresponding GitHub issue a 👍 so we know it’s important to you!
Hi Daniel, I think I can’t because I previously thumbs’upped in August – but anything I can do to bolster UI development is a must (I even previously asked the XAML team to redesign XAML based on ’embracing and extending’ HTML (one UI stack to rule them all), but hey! R
Can you use Windows AD within Blazor WASM?
I moved over to WASM and having some issue making restful post calls. Am getting 415 error and seem to have a hard time setting the content-type to application/json.
Am using an httpclient and httprequestmessage, any ideas on what could be the problem?
Thanks
Steve
Hi Steve. POSTing JSON should work fine. We provide a PostAsJson helper method for that purpose. Check the request in the browser dev tools and make sure the request content type header is what you expect.
With a Hosted Blazor app – Can you use a minimal Api approach and not controllers within the server project? Can a hosted solution with its server project hit windows AD just like a Server app?