<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Logging on Marko Apfel</title><link>http://blog.marko-apfel.de/tags/logging/</link><description>Recent content in Logging on Marko Apfel</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 02 Aug 2011 10:49:00 +0200</lastBuildDate><atom:link href="http://blog.marko-apfel.de/tags/logging/index.xml" rel="self" type="application/rss+xml"/><item><title>Performance-Analyzing of log4net regarding creation of new logger vs. taking an existing one</title><link>http://blog.marko-apfel.de/posts/performance-analyzing-of-log4net-regarding-creation-of-new-logger-vs-taking-an-existing-one/</link><pubDate>Tue, 02 Aug 2011 10:49:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/performance-analyzing-of-log4net-regarding-creation-of-new-logger-vs-taking-an-existing-one/</guid><description>&lt;h2 id="motivation"&gt;Motivation&lt;/h2&gt;
&lt;p&gt;During playing with AOP framework PostSharp I thought about the technique to weave the logger instances inside the code by using the CompileTimeInitialize–method. Unfortunately my logging-stuff must be serializable. This is not given. So I must use the other weaving point and access my Loggers.&lt;/p&gt;</description></item><item><title>Hierarchy of log4net-loggers (namespace vs class)</title><link>http://blog.marko-apfel.de/posts/hierarchy-of-log4net-loggers-namespace-vs-class/</link><pubDate>Thu, 20 Mar 2008 10:02:00 +0100</pubDate><guid>http://blog.marko-apfel.de/posts/hierarchy-of-log4net-loggers-namespace-vs-class/</guid><description>&lt;p&gt;If you want specify log-parameters for loggers of a whole namespace normally you use a scheme like&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-xml" data-lang="xml"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nt"&gt;&amp;lt;logger&lt;/span&gt; &lt;span class="na"&gt;name=&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;GrandNS.ParentNS.ChildNS.\*&amp;#34;&lt;/span&gt; &lt;span class="err"&gt;..&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;this is the same like&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-xml" data-lang="xml"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nt"&gt;&amp;lt;logger&lt;/span&gt; &lt;span class="na"&gt;name=&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;GrandNS.ParentNS.ChildNS&amp;#34;&lt;/span&gt; &lt;span class="err"&gt;..&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;There is no ambiguous name possible, because it is not allowed to define a class with the name of a namespace at the same namespace-level.&lt;/p&gt;</description></item></channel></rss>