Reputation: 381
I looked at the Common.Logging Nuget Package and the latest version supports .NET Core 1. I am currently using .NET Core 3. Hence I am looking for recommendations, whether it is still a good idea to use Common.Logging NuGet package, or is there any other alternate I should explore.
I am writing a NuGet package and one of the requirement is that it can take any logging object, mostly Log4Net or NLog object and log everything according to their configurations, which would be passed in from the parent project.
Upvotes: 2
Views: 1835
Reputation: 2245
My suggestion here is that you don't re-invent the wheel and use the Microsoft.Extensions.Logging libraries that Microsoft is bringing to manage the logging providers from a single point.
You have already some third-party connectors for NLog and Log4Net that simplifies the way to log in multiple providers, just registering each at startup level.
Upvotes: 2
Reputation: 26352
I think it's pretty safe. The https://www.nuget.org/packages/Common.Logging.Core/3.4.1 is for .net standard 1.0 and it seems there was no need to update.
In addition, based in this request https://github.com/net-commons/common-logging/issues/148 the project is still active with plans to support in the future.
From this question Are there any alternatives to Common.Logging?, it seems that there are no other valid alternatives but use it, or go for a custom facade implementation.
Upvotes: 0