<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Log4net on Marko Apfel</title><link>http://blog.marko-apfel.de/tags/log4net/</link><description>Recent content in Log4net 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/log4net/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>Break the mechanism, that GAC-assemblies could only bind to other GAC-assemblies</title><link>http://blog.marko-apfel.de/posts/break-the-mechanism-that-gac-assemblies-could-only-bind-to-other-gac-assemblies/</link><pubDate>Tue, 31 May 2011 08:30:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/break-the-mechanism-that-gac-assemblies-could-only-bind-to-other-gac-assemblies/</guid><description>&lt;p&gt;Till yet I thought, that if you have an assembly in the GAC all referenced assemblies must also be in the GAC. So a break of this GAC-assembly resolving chain is impossible.&lt;/p&gt;</description></item></channel></rss>