I'm getting ready for my first ASP.NET MVC 2 project and was wondering whether ASP.NET Tracing is sufficient for any logging I might need to do. Is anyone using a logging framework like log4net or NLog with an ASP.NET MVC 2 application, and if so, what additional functionality does it provide that ASP.NET Tracing lacks?
+1
A:
You should check out ELMAH. It does a lot for you. http://code.google.com/p/elmah/wiki/MVC
RonaldV
2010-10-12 15:45:22
Thanks, but I thought ELMAH only logged errors/exceptions?
adrift
2010-10-12 15:53:13
Yup, I guess I didn't totally get what you wanted. In any case tracing isn't really what you want running outside of developement/debugging purposes. When you want to log an important event within a project I would use log4net or better yet Common.Logging http://netcommon.sourceforge.net/ which supports a few logging libraries. You can also use them for debugging puposes by calling the Debug method if you wanted to... Use the right tool for the right job.
RonaldV
2010-10-12 22:08:59
A:
GIBRALTAR is an option if you're willing to consider a commercial solution. It integrates ASP.NET Tracing, ELMAH-like exception logging and ASP.NET Health Monitoring.
If you're interested, we have videos, full documentation and live chat on our website along with a full-featured 30-day trial.
Jay Cincotta
2010-10-12 17:51:49