Install
.NET CLI
dotnet add package Microsoft.Extensions.DependencyInjection --version 6.0.1
Package Manager Console
Install-Package Microsoft.Extensions.DependencyInjection -Version 6.0.1
PackageReference
<PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="6.0.1" />
Frameworks
Dependencies
Microsoft.Bcl.AsyncInterfaces
[6.0.0, )
.NETFramework4.6.1
Microsoft.Extensions.DependencyInjection.Abstractions
[6.0.0, )
.NETFramework4.6.1
System.Runtime.CompilerServices.Unsafe
[6.0.0, )
.NETFramework4.6.1
System.Threading.Tasks.Extensions
[4.5.4, )
.NETFramework4.6.1
[6.0.0, )
[6.0.0, )
Microsoft.Bcl.AsyncInterfaces
[6.0.0, )
.NETStandard2.0
Microsoft.Extensions.DependencyInjection.Abstractions
[6.0.0, )
.NETStandard2.0
System.Runtime.CompilerServices.Unsafe
[6.0.0, )
.NETStandard2.0
System.Threading.Tasks.Extensions
[4.5.4, )
.NETStandard2.0
Microsoft.Extensions.DependencyInjection.Abstractions
[6.0.0, )
.NETStandard2.1
System.Runtime.CompilerServices.Unsafe
[6.0.0, )
.NETStandard2.1
Adoption guide
Most ASP.NET Core and worker services that prioritize low ceremony and first-party integration.
Why it appears in the guide: Built-in DI container abstractions and implementation used by the default .NET hosting model. Trade-off: Advanced container features are intentionally minimal compared with full-featured third-party containers.
Compatibility metadata lists 4 target frameworks; confirm the exact target used by your application.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.