Here's a summary of what's new in ASP.NET Core in this preview release:
- Endpoint metadata on the developer exception page
- Added
InternalServerError
andInternalServerError<TValue>
toTypedResults
- Handle keyboard composition events in Blazor
ASP.NET Core updates in .NET 9 Preview 3:
- What's new in ASP.NET Core in .NET 9 documentation.
- Breaking changes
- Roadmap
.NET 9 Preview 3:
ASP.NET Core endpoints have associated metadata that can be used for a variety of purposes, like configuring routing, authentication and authorization, response caching, rate limiting, OpenAPI generation, and much more. The Routing tab of the ASP.NET Core developer exception page now desplays endpoint metadata alongside other routing information to facilitate debugging.
Thank you @Kahbazi for this contribution!
TypedResults
are a helpful vehicle for returning strongly-typed HTTP status code-based responses from a minimal API. The TypedResults
class now includes factory methods and types for returning "500 Internal Server Error" responses from your endpoints.
var app = WebApplication.Create();
app.MapGet("/", () => TypedResults.InternalServerError("Something went wrong!"));
app.Run();
Thank you @onurmicoogullari for this contribution!
The new KeyboardEventArgs.IsComposing
property indicates if the keyboard event is part of a composition session. This is useful for tracking the composition state of keyboard events, which is crucial for handling international character input methods.
Thank you @BattlefieldDuck for this contribution!
Thank you contributors! ❤️