http://blog.marko-apfel.de/tags/castle-windsor/Recent content in Castle Windsor on Marko ApfelHugoen-USTue, 03 May 2011 05:46:00 +0200http://blog.marko-apfel.de/posts/castle-windsor-order-of-configurations-and-resulting-resolvings/Tue, 03 May 2011 05:46:00 +0200http://blog.marko-apfel.de/posts/castle-windsor-order-of-configurations-and-resulting-resolvings/<p>If different implementations for the same interface are specified without named keys, then a resolving is made in order of the configurations. So the first fitting implementation is taken.</p> <p>Different implementations for the same interface is a typical scenario for patterns like “chain of responsibility” and “decorator”. If you want to describe such a chain you could use the next handler as a constructor- parameter in the actual one.</p>http://blog.marko-apfel.de/posts/castle-windsor-and-net-framwork-3-5-client-profil/Fri, 24 Sep 2010 17:32:00 +0200http://blog.marko-apfel.de/posts/castle-windsor-and-net-framwork-3-5-client-profil/<p>Today I have tried to use a <em>Castle Windsor</em> in an project based at <em>.NET Framwork 3.5 Client Profile</em>. This is not possible because somewhere in the Castle Windsor assembly a reference to <code>System.Web</code> is made.</p>http://blog.marko-apfel.de/posts/comparison-of-famous-ioc-containers/Wed, 08 Sep 2010 11:28:00 +0200http://blog.marko-apfel.de/posts/comparison-of-famous-ioc-containers/<h2 id="my-short-summary">My short summary</h2> <p>This comparison is mainly originated with attention to XML-based configuration possibilities and grouping implementations of the same contract which are to chose over a key.</p> <h2 id="structuremap">StructureMap</h2> <p>A really nice container with simple XML configuration. But we had problems if the container must instantiate WPF-controls.</p>