2

I'm working on a new ASP.NET application and I'm interested in using a recommended approach for logging. My question to the community is, what logging framework do you like to use on your ASP.NET projects? What are the pros / cons? There are so many and they seem to change all the time that I'm just not sure which road to go down.

Thank you

Branimir
  • 4,327
  • 1
  • 21
  • 33
user208662
  • 10,869
  • 26
  • 73
  • 86

5 Answers5

6

Log4Net

I've used Log4Net on a number of large projects, and it's always been reliable (and seems to be the majority of what my clients have been using already).

Ryan Hayes
  • 5,290
  • 4
  • 42
  • 52
4

"ELMAH (Error Logging Modules and Handlers) is an application-wide error logging facility that is completely pluggable. It can be dynamically added to a running ASP.NET web application, or even all ASP.NET web applications on a machine, without any need for re-compilation or re-deployment. "

http://code.google.com/p/elmah/

http://www.hanselman.com/blog/ELMAHErrorLoggingModulesAndHandlersForASPNETAndMVCToo.aspx

IrishChieftain
  • 15,108
  • 7
  • 50
  • 91
1

I've used at least 4 different logging frameworks, including the popular one mentioned by others. Personally, I would never use that framework if it were up to me--for lots of reasons.

My personal favorite is the object guy's logging framework found here. The only drawback is that it isn't free anymore. But it's practically free--and well-worth the time you'll save compared to trying to figure out some other frameworks.

Raj
  • 57
  • 2
0

I use Log4Net as well. It works very well and outputs to a multiple interfaces like text files, telnet, DB etc. I've found it to be easy to use and configure.

Simon
  • 6,062
  • 13
  • 60
  • 97
jmm312
  • 618
  • 1
  • 6
  • 17
-1

May be following two library, you could consider,

ELMAH

AnLogger

:)

user727071
  • 1
  • 1
  • this is a great example of low quality answer. The moment those links die, this answer is totally useless. – Tom Nov 03 '12 at 21:32