Microsoft.Extensions.DependencyInjection
Default implementation of dependency injection for Microsoft.Extensions.DependencyInjection.
Total Downloads
7.6B
7,636,526,072
Published
Jan 12, 2021
Latest stable version
Install
.NET CLI
dotnet add package Microsoft.Extensions.DependencyInjection --version 3.1.11
Package Manager Console
Install-Package Microsoft.Extensions.DependencyInjection -Version 3.1.11
PackageReference
<PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="3.1.11" />
Frameworks
Dependencies
Microsoft.Extensions.DependencyInjection.Abstractions
[3.1.11, )
.NETFramework4.6.1
Microsoft.Bcl.AsyncInterfaces
[1.1.1, )
.NETFramework4.6.1
Microsoft.Extensions.DependencyInjection.Abstractions
[3.1.11, )
.NETCoreApp3.1
Microsoft.Extensions.DependencyInjection.Abstractions
[3.1.11, )
.NETStandard2.0
Microsoft.Bcl.AsyncInterfaces
[1.1.1, )
.NETStandard2.0
Microsoft.Extensions.DependencyInjection.Abstractions
[3.1.11, )
.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.