docs: clarify thread safety of service resolution in .NET dependency … #50123
+9
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…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
Author
|
Hi @dotnet/docs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…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