ASP.NET Core Roadmap for .NET 9 · Issue #51834 · dotnet/aspnetcore (original) (raw)
This issue represents the list of major investments our team will focus on during the .NET 9 timeframe. It doesn't include all the features and bug fixes we'll be tackling during this time.
Note that this is an aspirational list of what we hope to get to. Many of these items will require thorough investigation and design, which can result in changes to our plans. We'll end up cutting some things and making changes as we go, but we'll try to keep this issue up to date to reflect on our progress and learnings.
There's a lot to discuss in the ASP.NET Core roadmap, and GitHub issue comments aren't great for multi-topic conversations, so we've set up the ASP.NET Core Roadmap for .NET 9 discussion to better handle these threaded conversations.
You can best express your support for specific GitHub issues by giving a 👍 reaction on the original post in the issue and by commenting with details about your scenarios and requirements. We try our best to prioritize work based on broad community support and feedback.
Servers/Scalability
- [Epic] Improve the Data Protection experience for apps with multiple instances #53654
- Epic: IDistributedCache updates in .NET 9 #53255
- Improve Kestrel metrics #53358
Minimal APIs
Blazor
Static Web Assets improvements
- Optimize file delivery for web apps #52824
- Append Hashes To Blazor Published Files #47575
- Move integrity support to the Static Web Assets SDK from the Blazor WebAssembly SDK #47000
Blazor Web improvements
- Add an API to tell you the current render mode #49401
- Provide a mechanism for rendering Blazor pages statically even when the app is set up for interactive rendering #51046