If you are using a corporate library, is it better to log4net to register?

For the project we use Enterprise Library 5 and we will use several blocks. I tend to use the Logging application block since its creation in this structure. But I see a lot of recommendations for log4net, therefore, what people have chosen, and if you choose log4net, why did you choose it over some of the others?

Thanks.

+6
c # logging enterprise-library log4net
source share
2 answers

I would probably go with an Enterprise Library registrar, since I usually prefer one integrated library using two separate libraries.

If you only used the registration block from EntLib, then I would probably choose log4net, but in this case, when you intend to use EntLib anyway, the advantages of log4net over EntLib are not enough to force them to drag another dependency for now.

+8
source share

Take a look at this question on SO: log4net vs. Nlog

The most voted answer seems particularly appropriate when comparing EntLib, log4net and NLog.

For what it's worth, I evaluated log4net and NLog and decided to go with NLog; I just wanted something that would be easy to set up and “just work”, and so far NLog has been one.

+9
source share

All Articles