All geek questions in one place

Which logging facades should I consider?

I looked through a bunch of old questions asking about entering .NET. A number of posts cited the use of logging facades to create a loose connection between the application and the selected logging structure. It seemed simple enough until I began to consider the scope of the journal. I looked at Common.Logging, which has interesting features, but it looks like development has stopped. And I looked at Windsor Castle, but that seems redundant if I just want to abstract the logging interface.

Most of the questions I found were older, so I hope the landscape has changed a bit. Is there a consensus on the “right” facade to use? Or should I just bite the bullet and register directly?

Thank!

+3
source share
3 answers

You should consider using a logging façade if you are developing a library that will be used by others and you do not want to force a specific logging implementation to be applied to it. I used Commons.Logging without any problems for this purpose in the past, although, as you noticed, the development seems to have stopped. It did not support my selection logger (NLog 2.x), and I had to compile it from the source to make it work (some time passed, so I don’t remember if I need to write any code, but I can see, 'interesting )

, . API, ( ), , .

NLog, log4net. XML, Enterprise Library . API - , .

+7

, , , . : ? , .

log4net: http://logging.apache.org/log4net/ Gibraltar ( ) http://www.gibraltarsoftware.com (, , ). log4net, .

+2

Trace .NET Framework . , , , , . .

0
source

Source: https://habr.com/ru/post/1795630/

More articles:


All Articles