-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft.Extensions work planned for .NET 7 #64015
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @dotnet/area-extensions-primitives Issue DetailsThis issue captures the planned work for .NET 7. This list is expected to change throughout the release cycle according to ongoing planning and discussions, with possible additions and subtractions to the scope. SummaryFor .NET 7 we are prioritizing the work to improve code reliability and minimize the number of high-impact bugs in the codebase. There's also some bottom up planned community requested feature requests available in the list. Planned for .NET 7
Logging Source Generator follow up (also listed in #52549)
post-release feedback
Testing and Documentation
Nullability
Planned for .NET 8+
|
Hi @maryamariyan - I'm happy to continue with #36390 Do we know yet what needs to be different this time around? We reached an impasse last time as we didn't want to change the declared type at runtime ( I'm please to hear that it's being considered again though, as I think this issue will be more and prevalent as projects are switched over to have Nullable Reference Types switched on: #52514 (comment) |
Thanks @SteveDunn for the interest let me get back to you on this on whether or not it would be marked for up for grabs. UPDATE: replied here |
Humble request to at least fix #36123 for PostgreSQL connection strings in .NET 7. I've created an issue in the docs to add a note about this bug as well. |
@geometrikal this need to be decided which way to consider for fixing according to the comment #36123 (comment). It is better not to rush this one now while we are trying to finish more priority work for .NET 7.0. Also, looks there is a workaround in the issue too. Thanks for your understanding. |
@tarekgh It looks like it was originally planned for .NET 6 then .NET 7 and now moved back to .NET 8. 😛 The experience of a user using app service and a PostgreSQL connection string (#36123 (comment)) has not changed in 2 years. The workaround is very simple but unfortunately the discoverability of it is low. Hopefully these comments change that! |
This issue captures the planned work for .NET 7. This list is expected to change throughout the release cycle according to ongoing planning and discussions, with possible additions and subtractions to the scope.
Summary
For .NET 7 we are prioritizing the work to improve code reliability and minimize the number of high-impact bugs in the codebase. There's also some bottom up planned community requested feature requests available in the list.
Planned for .NET 7
Hosting
Caching
Configuration
Logging
Logging Source Generator (also listed in #52549)
in
parameter modifier is present #62644post-release feedback
Testing and Documentation
Nullability
NativeAOT
Planned for .NET 8+
StackOverflowException when using Microsoft.Extensions.DependencyInjection #62239Windows service infrequently results in error 1067 on stop operation #62579Allow developers to use built-in meters for tracking stats on caches #67770[Feature Request] Allow libraries that don't use DI to make use of ILogger #50777DI : add support to eager load a singleton service #43149Add decorator extension methods to IServiceCollection #36021The text was updated successfully, but these errors were encountered: