Roadmap
This issue represents the list of major investments our team will focus on during .NET 6 timeframe.
The items on this list are only major areas of investments, and do not include all the features and bugfixes we will be tackling during this time.
Note, that this is an aspirational list of what we hope to get to. Many of the items on this list will require thorough investigations and design, which can result in changes in our plans. Hence, we may have to cut things as we go. We will try to keep this issue up to date to reflect on our progress and learnings.
General
Servers
MVC & APIs
Blazor
Cut
Roadmap
This issue represents the list of major investments our team will focus on during .NET 6 timeframe.
The items on this list are only major areas of investments, and do not include all the features and bugfixes we will be tackling during this time.
Note, that this is an aspirational list of what we hope to get to. Many of the items on this list will require thorough investigations and design, which can result in changes in our plans. Hence, we may have to cut things as we go. We will try to keep this issue up to date to reflect on our progress and learnings.
General
Servers
MVC & APIs
Blazor
blazorwasmdebug type in VS Code #22587Cut
[ ] Expose location changing event for NavigationManger #14962[ ] Specific components for dealing with large binary data (files and media) #30290[ ] Ability to monitor circuit activity #30287[ ] Pause and resume Blazor applications #27576[ ] Drag & Drop #18754[ ] [EPIC]: Bedrock Endgame #15005[ ] [Kestrel] Tooling around connection refused on app restart #27463[ ] Developers can safely trim ASP.NET apps to reduce their deployment payloads #27384[ ] Improve single-file-publishing for ASP.NET #27888[ ] Improvements to web api experience around OpenAPI and API Explorer #27889[ ] Epic: Blazor developers can target and deploy their applications to desktop platforms, allowing them to run natively maui#2536[ ] [Epic] SignalR should have a C++ client #5301