My blog has moved and can now be found at

No action is needed on your part if you are already subscribed to this blog via e-mail or its syndication feed.

Tuesday, December 7, 2004
« Web services Contract-First Design & Dev... | Main | IEEE Security & Privacy: Building Securi... »

I just got back from the CMAP .NET User Group meeting during which I did 2 short presentations. At CMAP's December meetings we have a "10 Tips & Tricks for the Holidays" presentation format in which members do short 10-15 minute presentations on various topics. This year's topics ranged from my stuff to a demo of how to use client side script in ASP.NET.  My topics were "Instrumenting .NET Code with Log4Net" and "Applying Defense-in-Depth to protecting admin sections of web sites". 

During the instrumenting & logging presentation I mentioned that K. Scott Allen has a great write-up on Diagnostics and Logging in ASP.NET and that people should check it out to get a background on the "Why?" regarding instrumenting applications. Then I went into a short description of what Log4Net brought to the table and compared it to the PAG's Exception Management Block and the Logging Block.  In addition, I also had an earlier blog entry about incorporating logging into a web application.

My Defense-in-Depth short presentation was an expansion of an earlier blog entry that I had made on this topic.

Tags:: Security
12/7/2004 10:08 PM Eastern Standard Time  |  Comments [1]  |  Disclaimer  |  Permalink   
Sunday, May 8, 2005 12:06:42 AM (Eastern Daylight Time, UTC-04:00)
I've gone through implementing log4net in ASP.NET applications a few times now. I've documented my issues in a log4net tutorial at:
<br>log4net Tutorial: Using log4net in an ASP.NET Application
<br><a target="_new" href=""></a>
<br>Here are 2 lines of code you may want to use to start out your methods:
<br> log4net.Config.DOMConfigurator.Configure(new System.IO.FileInfo(AppDomain.CurrentDomain.SetupInformation.ConfigurationFile) );
<br> log4net.ILog log = log4net.LogManager.GetLogger(System.Reflection.MethodBase.GetCurrentMethod().DeclaringType);
Tom Gilkison
Comments are closed.