Skip to content

Clarify automatic disposal for all service lifetimes in DI guidelines #51384

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.

Sign up for GitHub

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

Merged
gewarren merged 4 commits into from
Feb 3, 2026
+4 −1
Merged

Clarify automatic disposal for all service lifetimes in DI guidelines #51384

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d019a4b
Initial plan
Copilot Jan 28, 2026
32b9d2d
Clarify disposal behavior for all service lifetimes
Copilot Jan 28, 2026
1e3f532
Improve clarity and consistency in disposal documentation
Copilot Jan 28, 2026
051fbcc
Update docs/core/extensions/dependency-injection/guidelines.md
gewarren Jan 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/core/extensions/dependency-injection/guidelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,10 @@ If a class has many injected dependencies, it might be a sign that the class has

### Disposal of services

The container is responsible for cleanup of types it creates, and calls <xref:System.IDisposable.Dispose%2A> on <xref:System.IDisposable> instances. Services resolved from the container should never be disposed by the developer. If a type or factory is registered as a singleton, the container disposes the singleton automatically.
The container is responsible for cleanup of types it creates, and calls <xref:System.IDisposable.Dispose%2A> on <xref:System.IDisposable> instances. Services resolved from the container should never be disposed by the developer. The container disposes services automatically based on their lifetime:

- **Transient** and **scoped** services are disposed at the end of the scope in which they were resolved. In apps that process requests, this is typically at the end of the request.
- **Singleton** services are disposed when the service container is disposed, usually at application shutdown.

In the following example, the services are created by the service container and disposed automatically:

Expand Down