-
Hi Mark, Erich,
Thank you for the quick fix!
I now use CommonLogging in all my projects, and I love it. Thank you so much for the community contribution!
Sorry for the late response. For some reason I didn't get notification on any updates on this.
Best regards,
Martin.
2010-01-07 00:31:29 UTC by Martin
-
fixed by simple converting a source to string.Empty before formatting the loggername.
2009-12-14 10:50:55 UTC by oakinger
-
oakinger committed revision 166 to the Common Infrastructure Libraries for .NET SVN repository, changing 2 files.
2009-12-14 10:49:54 UTC by oakinger
-
oakinger committed revision 165 to the Common Infrastructure Libraries for .NET SVN repository, changing 2 files.
2009-12-14 10:48:19 UTC by oakinger
-
there is a lock, don't worry.
2009-12-14 10:39:10 UTC by oakinger
-
oakinger committed revision 164 to the Common Infrastructure Libraries for .NET SVN repository, changing 5 files.
2009-12-13 03:46:02 UTC by oakinger
-
When launched from commandline, the log is ok. Using F5 in VS the loggername is wrong:
2009-12-11 21:52:46,769 [1] INFO [MainApplication.Program.Main] - Start Common Logging example
2009-12-11 21:52:46,831 [1] DEBUG [MainApplication.InsideClass.ReallyDeepMethod] - inside another class...
2009-12-11 21:52:46,831 [1] INFO [MainApplication.Program.Main] - End Common Logging example...
2009-12-11 20:59:12 UTC by nobody
-
Thanks so much for reporting this!
2009-12-09 16:07:36 UTC by markpollack
-
Another alternative solution might be to not pass null into the Log method from it's usages:
CommonLoggingTraceListener.cs
267 ///
268 /// Writes message to logger provided by .
269 ///
270 public override void Write(string message)
271 {
272 if (((this.Filter == null...
2009-12-09 00:29:45 UTC by Martin
-
When System.Diagnostics.Trace to routed to send its output to the Common.Logging infrastructure using the CommonLoggingTraceListener:
app.config
...
2009-12-09 00:25:02 UTC by Martin
