Replace log4net with microsoft.extensions.logging.abstractions about resin HOT 7 CLOSED

You can use your own logger with log4net last I checked...

http://www.alteridem.net/2008/01/10/writing-an-appender-for-log4net/

from resin.

Sure, I know that works, but I don't want to drag in an extra logging library, when I already have (another) one fully working.
Packages should not implement/dependent on a concrete logging library, but should log to an abstraction of it and let the actual logging be as a responsibility of the application that uses the package. In other words, freedom of choice!

from resin.

Another alternative might be liblog which is an abstraction especially for 3rd party libraries (https://github.com/damianh/LibLog). Both do basically the same: provide a logging abstraction.

from resin.

Thank you for taking an interest in the Resin codebase and sorry for waiting a month before answering.

@bravecobra Sure, I'm also allergic to dependencies. I f-ing love log4net though. Didn't realize not all people use it. What would you prefer, between the two alternatives you gave, as a means for a logging abstraction layer?

from resin.

Fixed here: 5f85425

from resin.

Sorry for closing issue without fully addressing the issue (of not using a MS standardized logging interface).

from resin.

Fixed here: b36c01e

from resin.