I actually found a way to do this in this thread: http://www.l4ndash.com/Log4NetMailArchive/tabid/70/forumid/1/postid/18271/view/topic/Default.aspx I’ve tested the first method and it works. Just in case that link is not longer good I’ll reproduce the code here. Basically the author states that there are two ways of doing this. First way: Create a new locking model that only … Read more
You need to create the database and the Log table yourself. If you want to diagnose possible issues with log4net, you can create a diagnostic trace by adding this to your .config file: <system.diagnostics> <trace autoflush=”true”> <listeners> <add name=”textWriterTraceListener” type=”System.Diagnostics.TextWriterTraceListener” initializeData=”C:\whatever\your\path\is\log4net.txt” /> </listeners> </trace> </system.diagnostics> and adding the debug switch: <appSettings> <add key=”log4net.Internal.Debug” value=”true”/> </appSettings>