docs: clarify thread safety of service resolution in .NET dependency … #50123
Conversation
…injection ### Summary Clarified that resolving services from the built-in .NET dependency injection (DI) container is thread-safe. ### Changes - Updated the **Thread safety** section in `dependency-injection-guidelines.md`. - Added explicit statement that: - Service resolution via `IServiceProvider` and `IServiceScope` is thread-safe. - Service implementations themselves must still handle internal concurrency. - Added a note block for clarity. ### Motivation Resolves issue dotnet#47086 by explicitly documenting DI service resolution thread safety, which was previously implied but not stated.
dotnet-policy-service
bot
added
dotnet-fundamentals/svc
community-contribution
|
Hi @dotnet/docs |
Clarify thread safety and recommendations for DI usage.
|
Hi @IEvangelist, |
Updated the dependency injection guidelines to improve clarity and correctness in the documentation.
|
|
||
| - Property injection | ||
| - Injection based on name (.NET 7 and earlier versions only. For more information, see [Keyed services](dependency-injection.md#keyed-services).) | ||
| - Injection based on name (.NET 7 and earlier versions only–for more information, see [Keyed services](dependency-injection.md#keyed-services)) |
There was a problem hiding this comment.
This item may give the wrong impression that injection based on name is only available in .NET 7 and earlier versions.
Now that .NET 7 is no longer supported, and later versions of Microsoft.Extensions.DependencyInjection still target .NET Standard 2.0 too, it might be better to remove the item altogether.
4 participants
…injection
Summary
Clarified that resolving services from the built-in .NET dependency injection (DI) container is thread-safe.
Changes
dependency-injection-guidelines.md.IServiceProviderandIServiceScopeis thread-safe.Motivation
Resolves issue #47086 by explicitly documenting DI service resolution thread safety, which was previously implied but not stated.
Summary
Describe your changes here.
Fixes #Issue_Number (if available)
Internal previews