Skip to main content

If you are a library or framework author and you wish to provid logging support to your component there are a couple of options 1) Depend on Log4Net/NLog 2) Depend on Common.Logging 3) Implement your own ILog interface and make your consumers wire it up. Option 1 is not desirable because it forces your users to use a particular framework. Option 2 is not desirable because it will add yet more nuger package dependencies and project references with associated versioning concerns and requires wiring up with. Option 3 is desirable because it is dependency free but requires that your users to remember to write an adapter and wire things up. This package is a version of option 3: - It will add an ILog, ILogProvider etc to YourRootNamespace.Logging - ILog is 2 methods to implement in comparision to Common.Logging ILog's ~65 members - Using reflection, it transparently supports NLog and Log4Net without any wiring up required by an end user.

Total Downloads
5.6M
5,636,001
Published
Sep 6, 2014
Latest stable version

Install

.NET CLI
dotnet add package LibLog --version 1.0.0-beta2
Package Manager Console
Install-Package LibLog -Version 1.0.0-beta2
PackageReference
<PackageReference Include="LibLog" Version="1.0.0-beta2" />

Frameworks

No framework metadata available.

Dependencies

No declared dependencies.

Adoption guide

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

This version is marked prerelease. Validate its API and upgrade path before production use.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.

No target framework metadata is available. Confirm compatibility in a representative project before standardising on this package.

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.