我认为一般的共识是nlog更容易配置和使用。不过，两者都很有能力。

正如我注意到的那样，log4net在应用程序运行的整个过程中都会锁定它们的输出文件，因此不能删除它们。除此之外，它们是相似的。

所以我更喜欢NLog。

我认为一般的共识是nlog更容易配置和使用。不过，两者都很有能力。

由于最近使用过这两个框架，我想我可以分享一下我对这两个框架的看法。

我被要求评估现有web应用程序的日志框架，在浏览了各种在线论坛后，我将选择范围缩小到NLog (v2.0)和log4net (v1.2.11)。以下是我的发现:

Setting/starting up with NLog is dead easy. You go through the Getting started tutorial on their website and you are done. You get a fair idea, how thing might be with nlog. Config file is so intuitive that anyone can understand the config. For example: if you want to set the internal logging on, you set the flag in Nlog config file's header node, which is where you would expect it to be. In log4net, you set different flags in web.config's appSettings section. In log4net, internal logging doesnt output timestamp which is annoying. In Nlog, you get a nice log with timestamps. I found it very useful in my evaluations. Filters in log4net - You better check my this question - log4net filter - how to write AND filter to ignore log messages and if you find an answer/solution for this, please let me know. I understand, there is a workaround for this question, as you can write your own custom filter. But something which is not easily available in log4net. Performance - I logged around 3000 log messages to database using a stored procedure. I used simple for loop (int i=0; i<3000; i++... to log the same message 3000 times. For the writes: log4net AdoAppender took almost double the time than NLog. Log4net doesnt support asynchronous appender.

经过比较，我选择了NLog作为日志框架。:)

嗯. .我使用Enterprise库执行数据库日志记录任务 现在由于性能瓶颈，我切换到NLog。

一些比较信息:

http://pauliusraila.blogspot.com/2010/10/solving-database-logging-bottlenecks.html

我也支持NLog，因为它也可以处理非托管代码。 我认为可以同时使用log4net和log4cxx，但是NLog同时处理托管和非托管代码。

我还看了Common。日志，一个对日志api进行抽象的facade，它支持log4net, NLog和enterprise Library。我不认为我会使用它，但我喜欢他们如何使用lambdas来提高日志记录被禁用时的性能(一个与NLog和其他可能共享的特性)。