ASP.NET Core planning for .NET 11 is now in progress! This roadmap is currently just a placeholder. We'll update the roadmap with specific planned features as planning progresses.
This issue represents the list of major investments our team will focus on during the .NET 11 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 a discussion topic 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.
Proposed themes:
- Address top feedback & pain points
- Fundamentals
- Performance, security, observability, reliability
- Invest in our modern stack
- Minimal APIs, Blazor, SignalR, gRPC
- Simplify building distributed web apps
- Enable building agentic web apps
- Copilot-assisted web development
Servers and APIs
Kestrel
Middleware
Fundamentals
APIs
SignalR
Authentication and Identity
Blazor
Static server-side rendering
Routing
Interactive Server
WebAssembly
Aspire integration
Virtualize
Address top asks and pain points
ASP.NET Core planning for .NET 11 is now in progress! This roadmap is currently just a placeholder. We'll update the roadmap with specific planned features as planning progresses.
This issue represents the list of major investments our team will focus on during the .NET 11 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 a discussion topic 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.
Proposed themes:
Servers and APIs
Kestrel
Middleware
Fundamentals
APIs
SignalR
Authentication and Identity
Follow-ups for passkey support in ASP.NET Core Identity #62347Blazor
Static server-side rendering
Routing
Nested Routing In Blazor #11212Blazor Custom Route Constraints #28938Interactive Server
WebAssembly
Aspire integration
Virtualize
Address top asks and pain points
[Blazor] Framework support for per-page JavaScript logic #52273Introduce the concept of state transitions in Blazor to allow for e.g. animations #10389Enabledebounce/throttlingfor events #10522Revisit hot reload browser refresh script injection #45213Blazor Server keep-alive & reconnection issues #48724[Blazor] Improve the experience with QuickGrid and EF Core #58716