Not planned
Description
Super early list of potential areas to investigate in .NET 7:
- More OpenAPI
- describe schemas, either from binders or metadata
- query/header/path params
- more automatic descriptions (less need to use manual metadata)
- easier authn/z configuration with Swagger UI light-up
- More inferred parameter binding
- Form & File binding
- etc.
- Extensible parameter binding
- Extensible Result processing, e.g. delayed execution, shortcutting
- Validation
- Hot Reload, e.g. top-level statements, modifying route mappings, DI, etc.
- Composition, e.g.
- Route grouping
- Route handler filters
- 3rd-party extensibility
- nSwag
- OData
- Microsoft....ApiVersioning
- Developer experience
- Route debugging tool/features
- Analyzers
- API versioning
- Trimming and AoT
- Performance
- Problem Details everything
- DeveloperExceptionPage
- Middleware/ExceptionHandler
- Something else?
- Anti-forgery support (XSRF), e.g. via a middleware
- Teach MVC to do more stuff like Minimal APIs, e.g. auto service resolution
- Expanding the minimalistic philosophy to other areas of ASP.NET Core
- CORS
- Authn/z
- gRPC, SignalR, Orleans
- Razor support (e.g.
Results.Page()
)
Metadata
Metadata
Assignees
Labels
Type
Projects
Relationships
Development
No branches or pull requests
Activity
shaggygi commentedon Sep 21, 2021
Bedrock? Just curious.
loic-sharma commentedon Oct 17, 2021
Would introducing minimal APIs for generic hosts and worker services make sense?
gulshan commentedon Oct 17, 2021
Please keep asp.net core 7 runnable on .net 6 LTS runtime.
davidfowl commentedon Oct 17, 2021
They ship together so that won't happen
ghost commentedon Oct 11, 2022
Thanks for contacting us.
We're moving this issue to the
.NET 8 Planning
milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.
DamianEdwards commentedon Jan 26, 2023
Closing this issue as many of these are done or tracked by other issues now.