tag:blogger.com,1999:blog-38895959.post2448044949574486223..comments2010-02-19T14:28:13.650ZSimon Harthttp://www.blogger.com/profile/08526568682625258690noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-38895959.post-49218145890592955362010-02-19T14:28:13.650Z2010-02-19T14:28:13.650ZHi Daniel,<br /><br />You need to do that anyway whether you choose to use a service locator or not. This is a limitation of singleton factories - which is why people say they are hard to test. Of course not all factories are singletons!<br /><br />The common service locator is just another layer to setup.<br /><br />Cheers<br />SimonSimon Harthttp://www.blogger.com/profile/08526568682625258690noreply@blogger.comtag:blogger.com,1999:blog-38895959.post-34223807943496393202010-02-19T06:01:26.351Z2010-02-19T06:01:26.351ZHy Simon<br />With &quot;injection of dependenies in singleton&quot; I meant the setup stage in your test where you need to exchange the dependencies in your service locator with mocks/stubs etc.<br /><br />DanielDaniel Marbachhttp://www.planetgeek.chnoreply@blogger.comtag:blogger.com,1999:blog-38895959.post-61643082150027444012010-02-19T05:35:16.027Z2010-02-19T05:35:16.027ZHi Daniel,<br /><br />The CSL is really about abstracting the IoC container from client code where DI is not possible. For example factory classes or singletons not all classes are added to the container so can&#39;t be injected.<br /><br />Yes this makes TDD slightly more difficult in that it is an extra layer of stuff to setup before testing can be done but it&#39;s not that painful. Not sure what you mean by &quot;injection of dependenies in singleton?&quot; <br /><br />ninject is very heavyweight for device dev whic is why I&#39;ve stayed away from it.<br /><br />Cheers<br />Simon.Simon Harthttp://www.blogger.com/profile/08526568682625258690noreply@blogger.comtag:blogger.com,1999:blog-38895959.post-91346623140103321222010-02-17T20:38:29.195Z2010-02-17T20:38:29.195ZHy Simon,<br />I&#39;m really against using Common Service Locator. For me the correct way of using an Inversion of Control container is that only a really small portion of the code should be aware of the IoC. Most of the classes should only declare their mandatory dependencies in their constructor and their non mandatory dependencies by property. I generally avoid usage of attributes etc. If one needs to dynamically create instances on request a factory should encapsulate the IoC mechanism. This makes the code clean and the DI exchangeable. Common Service Locator is a nightmare when it comes to TDD (injection of dependencies in singleton, cleanup, tests are not isolated in worst case). I would rather put effort into porting the ideas of nate&#39;s ninject etc. to compact framework. In fact there are some people around ninject community which are currently trying to port ninject latest trunk to CF.<br /><br />DanielDaniel Marbachhttp://www.planetgeek.chnoreply@blogger.com