CODEWITHSUNDEEP
.netlogging
Andrew Florko
Andrew Florko

Reputation: 7750

.NET Logger libraries. Your choice

What logger library you use in .NET projects and the one you prefer? I used log4net for a while, but it's last version is 2007. What is your personal choice and your opinion if you had hands on several libraries? Is there a logger library that is production standard nowadays?

Thank you in advance!

Upvotes: 4

Views: 413

Answers (5)

Jeremy Wiebe
Jeremy Wiebe

Reputation: 3963

Two that I know of are log4net. I've used this on numerous projects. The documentation is decent although I always have to read the docs to get a new project set up.

There is also NLog although I haven't used it.

Upvotes: 1

Ron Klein
Ron Klein

Reputation: 9450

I still use log4net. No complaints.

Upvotes: 4

Steven
Steven

Reputation: 172646

I prefer my own CuttingEdge.Logging. I built it, because I was a bit annoyed with the complexity logging frameworks such as Log4net and Logging Application Block. CuttingEdge.Logging is easy to use, but sacrifices flexibility for this.

Upvotes: 1

Yauheni Sivukha
Yauheni Sivukha

Reputation: 2596

Logging Application Block from Microsoft Enterprise Library is not bad one.

List of advantages:

  1. It can write to the various predefined destinations - database, Event log, Text file, Remote server by MSMQ and It also supports custom writers.
  2. Configuration can be done trough external tool, which works directly with your application app.config or dynamically in runtime.
  3. Support from Microsoft. 5 version released on April 2010

Upvotes: 4

Alan
Alan

Reputation: 46813

I personally can't stand log4net. If you use a log4j, then maybe it makes sense, but if you're starting from an uncorrupted mind, you're going to wonder why it's written the way it is.

I prefer The Object Guy's Dot Net Logger.

Upvotes: 3

Related Questions