<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Again on castle windsor and default component</title>
	<atom:link href="http://www.codewrecks.com/blog/index.php/2008/05/27/again-on-castle-windsor-and-default-component/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.codewrecks.com/blog/index.php/2008/05/27/again-on-castle-windsor-and-default-component/</link>
	<description>Wrecks of code floating in the sea of Internet</description>
	<lastBuildDate>Wed, 28 Jul 2010 15:30:03 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Craigology</title>
		<link>http://www.codewrecks.com/blog/index.php/2008/05/27/again-on-castle-windsor-and-default-component/comment-page-1/#comment-1582</link>
		<dc:creator>Craigology</dc:creator>
		<pubDate>Thu, 19 Jun 2008 14:08:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.codewrecks.com/blog/index.php/2008/05/27/again-on-castle-windsor-and-default-component/#comment-1582</guid>
		<description>Thanks, a big help!

We had a situation where the interface type was declared twice in the container, once for WCF client proxies and once once for the WCF service implementations. We wanted to enforce that the client proxy is the default implementation returned, and were hoping that the order of declaration in the Windsor config would enforce this, but it seems that this is not guaranteed when dependencies in the object graph come into play.

Your technique now ensures that we can always specify which implementation is resolved by default. This is even more important during injection, since it is obviously not possible there to disambiguate by supplying a key as you would in a direct call to Resolve(string key).

Thanks again.
Craig.</description>
		<content:encoded><![CDATA[<p>Thanks, a big help!</p>
<p>We had a situation where the interface type was declared twice in the container, once for WCF client proxies and once once for the WCF service implementations. We wanted to enforce that the client proxy is the default implementation returned, and were hoping that the order of declaration in the Windsor config would enforce this, but it seems that this is not guaranteed when dependencies in the object graph come into play.</p>
<p>Your technique now ensures that we can always specify which implementation is resolved by default. This is even more important during injection, since it is obviously not possible there to disambiguate by supplying a key as you would in a direct call to Resolve(string key).</p>
<p>Thanks again.<br />
Craig.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
