Install
.NET CLI
dotnet add package Microsoft.Extensions.Logging --version 3.1.17
Package Manager Console
Install-Package Microsoft.Extensions.Logging -Version 3.1.17
PackageReference
<PackageReference Include="Microsoft.Extensions.Logging" Version="3.1.17" />
Frameworks
Dependencies
Microsoft.Extensions.Configuration.Binder
[3.1.17, )
.NETCoreApp3.1
Microsoft.Extensions.DependencyInjection
[3.1.17, )
.NETCoreApp3.1
Microsoft.Extensions.Logging.Abstractions
[3.1.17, )
.NETCoreApp3.1
Microsoft.Extensions.Options
[3.1.17, )
.NETCoreApp3.1
Microsoft.Extensions.Configuration.Binder
[3.1.17, )
.NETStandard2.0
Microsoft.Extensions.DependencyInjection
[3.1.17, )
.NETStandard2.0
Microsoft.Extensions.Logging.Abstractions
[3.1.17, )
.NETStandard2.0
Microsoft.Extensions.Options
[3.1.17, )
.NETStandard2.0
Adoption guide
Applications that want provider-agnostic logging and straightforward integration with .NET hosts.
Why it appears in the guide: The standard logging abstraction and default implementation used throughout modern .NET hosting. Trade-off: Advanced routing and event shaping are supplied by providers or additional configuration, not the abstraction alone.
Compatibility metadata lists 2 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.