I put log4net.dll into the global assembly cache, because it's just easier that way.
Here is the complete listing of my Web.config. Relevant excerpts below:
Code:
<log4net debug="true">
<appender name="rollingFile" type="log4net.Appender.RollingFileAppender,log4net">
<param name="File" value="/var/www/zapocalypse/log.txt" />
<param name="AppendToFile" value="true" />
<param name="RollingStyle" value="Date" />
<param name="DatePattern" value="yyyy.MM.dd" />
<param name="StaticLogFileName" value="true" />
<param name="CountDirection" value="1" />
<layout type="log4net.Layout.PatternLayout,log4net">
<param name="ConversionPattern" value="%d [%t] %-5p %c [%x] <%X{auth}> - %m%n" />
</layout>
</appender>
<root>
<priority value="ALL" />
<appender-ref ref="rollingFile" />
</root>
</log4net>
How can I tell whether log4net is successfully parsing the configuration data in Web.config?
What are some possible reasons that it would fail to work?
Is NHibernate just very, very quiet in its logs?
Login
FAQ
Search