Better logging about chocolateygui HOT 8 CLOSED

What's the big difference between these two?

from chocolateygui.

Log4net had been dead for a few years, while nlog is being actively developed. Lately log4net has come back alive but the signed their assemblies and made a mess of the versioning.

This.log is an easy way to include logging in your code since it no longer needs you to add private ILog log = ... to every class. You can just do this.Log.Debug("...") and it will pick the classname from that.

from chocolateygui.

Okay, that's good to know.

from chocolateygui.

Thinking about this, and having not looked too closely at the code yet, do we need to abstract this into an interface, and then use the IoC Container to provide a specific instance on the interface, rather than taking a direct dependency on a specific logging framework?

from chocolateygui.

No, this.log abstracts it away for you. No need to inject since it is an extension method.

from chocolateygui.

Cool, I really need to check out this package :-)

from chocolateygui.

This is my current nlog config for rollingfileappender.

<nlog>
    <targets>
      <target name="file" type="File" fileName="${basedir}/logs/chocolateygui_${level}.log" layout="${longdate} ${threadid} [${level:uppercase=true}] ${logger} ${message}" archiveFileName="${basedir}/logs/chocolateygui_${level}.{#}.log" archiveAboveSize="1048576" archiveNumbering="Sequence" maxArchiveFiles="10" concurrentWrites="true" keepFileOpen="false" encoding="iso-8859-2" />
    </targets>
    <rules>
      <logger name="*" minlevel="Debug" writeTo="file" />
    </rules>
  </nlog>

from chocolateygui.

Hold on a minute...

Where are the other 20 odd lines of XML that is normally required?!? :-P

from chocolateygui.