<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blog.vuscode.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Design for testability - Microsoft Unity (part 7)</title><link>http://blog.vuscode.com/malovicn/archive/2008/05/18/design-for-testability-microsoft-unity-part-7.aspx</link><description>On my quest to design for testability, I&amp;#39;ve already covered: Part 1 - Separation of concerns (SOC) by encapsulating DAL code in internal provider class Part 2 - Decoupling manager and provider class (introducing the IProvider) Part 3 - Decoupling</description><dc:language>en</dc:language><generator>CommunityServer 2007 (Build: 20416.853)</generator><item><title>Model View Presenter (MVP) – Tips from trenches (TFT) – Base types(Part 1)</title><link>http://blog.vuscode.com/malovicn/archive/2008/05/18/design-for-testability-microsoft-unity-part-7.aspx#589</link><pubDate>Mon, 19 Jan 2009 13:48:03 GMT</pubDate><guid isPermaLink="false">4fad33ed-6fa7-4667-b447-1fa3be86b49e:589</guid><dc:creator>VusCode - Coding dreams since 1998!</dc:creator><description>&lt;p&gt;RAD tooling style Microsoft is supporting last couple of years usually leads to the code where presentation and bossiness logic are mixed and tightly coupled which makes testability, maintainability and sustainability much more harder then they should&lt;/p&gt;
&lt;img src="http://blog.vuscode.com/aggbug.aspx?PostID=589" width="1" height="1"&gt;</description></item><item><title>re: Design for testability - Microsoft Unity (part 7)</title><link>http://blog.vuscode.com/malovicn/archive/2008/05/18/design-for-testability-microsoft-unity-part-7.aspx#529</link><pubDate>Sun, 09 Nov 2008 21:29:26 GMT</pubDate><guid isPermaLink="false">4fad33ed-6fa7-4667-b447-1fa3be86b49e:529</guid><dc:creator>Simon Brangwin</dc:creator><description>&lt;p&gt;Thanks for the great article Nikola. Your idea to abstract the IOC container behind the ServiceLocator is genius.&lt;/p&gt;
&lt;img src="http://blog.vuscode.com/aggbug.aspx?PostID=529" width="1" height="1"&gt;</description></item><item><title>how to remove search setter 1 1</title><link>http://blog.vuscode.com/malovicn/archive/2008/05/18/design-for-testability-microsoft-unity-part-7.aspx#445</link><pubDate>Thu, 10 Jul 2008 11:19:19 GMT</pubDate><guid isPermaLink="false">4fad33ed-6fa7-4667-b447-1fa3be86b49e:445</guid><dc:creator>how to remove search setter 1 1</dc:creator><description>&lt;p&gt;Pingback from &amp;nbsp;how to remove search setter 1 1&lt;/p&gt;
&lt;img src="http://blog.vuscode.com/aggbug.aspx?PostID=445" width="1" height="1"&gt;</description></item><item><title>design for testability</title><link>http://blog.vuscode.com/malovicn/archive/2008/05/18/design-for-testability-microsoft-unity-part-7.aspx#439</link><pubDate>Fri, 04 Jul 2008 18:51:36 GMT</pubDate><guid isPermaLink="false">4fad33ed-6fa7-4667-b447-1fa3be86b49e:439</guid><dc:creator>design for testability</dc:creator><description>&lt;p&gt;Pingback from &amp;nbsp;design for testability&lt;/p&gt;
&lt;img src="http://blog.vuscode.com/aggbug.aspx?PostID=439" width="1" height="1"&gt;</description></item><item><title>re: Design for testability - Microsoft Unity (part 7)</title><link>http://blog.vuscode.com/malovicn/archive/2008/05/18/design-for-testability-microsoft-unity-part-7.aspx#417</link><pubDate>Thu, 29 May 2008 12:39:23 GMT</pubDate><guid isPermaLink="false">4fad33ed-6fa7-4667-b447-1fa3be86b49e:417</guid><dc:creator>Nikola Malovic</dc:creator><description>&lt;p&gt;The main reason was that I was deadmarching to meet one important deadline for couple of weeks and didn't have time to finish entry application team was supposed to provide in order to compete..&lt;/p&gt;
&lt;p&gt;I'm really sorry to miss that because I'm sure that was A LOT of fun &lt;/p&gt;
&lt;p&gt;I don't know id WYW would be next year, but in case it does I am taking vacation on time for that :)&lt;/p&gt;
&lt;img src="http://blog.vuscode.com/aggbug.aspx?PostID=417" width="1" height="1"&gt;</description></item><item><title>re: Design for testability - Microsoft Unity (part 7)</title><link>http://blog.vuscode.com/malovicn/archive/2008/05/18/design-for-testability-microsoft-unity-part-7.aspx#413</link><pubDate>Mon, 26 May 2008 12:21:38 GMT</pubDate><guid isPermaLink="false">4fad33ed-6fa7-4667-b447-1fa3be86b49e:413</guid><dc:creator>Andrew</dc:creator><description>&lt;p&gt;hey Nicola why didn't you come to WinTheWeb last weekend?&lt;/p&gt;
&lt;img src="http://blog.vuscode.com/aggbug.aspx?PostID=413" width="1" height="1"&gt;</description></item><item><title>re: Design for testability - Microsoft Unity (part 7)</title><link>http://blog.vuscode.com/malovicn/archive/2008/05/18/design-for-testability-microsoft-unity-part-7.aspx#412</link><pubDate>Sun, 25 May 2008 07:57:30 GMT</pubDate><guid isPermaLink="false">4fad33ed-6fa7-4667-b447-1fa3be86b49e:412</guid><dc:creator>Dan</dc:creator><description>&lt;p&gt;Another great post, thank you. I'm writing better code after reading your series about design for testability.&lt;/p&gt;
&lt;img src="http://blog.vuscode.com/aggbug.aspx?PostID=412" width="1" height="1"&gt;</description></item><item><title>Design for testability - Microsoft Unity (part 7)</title><link>http://blog.vuscode.com/malovicn/archive/2008/05/18/design-for-testability-microsoft-unity-part-7.aspx#407</link><pubDate>Thu, 22 May 2008 10:33:48 GMT</pubDate><guid isPermaLink="false">4fad33ed-6fa7-4667-b447-1fa3be86b49e:407</guid><dc:creator>DotNetKicks.com</dc:creator><description>&lt;p&gt;You've been kicked (a good thing) - Trackback from DotNetKicks.com&lt;/p&gt;
&lt;img src="http://blog.vuscode.com/aggbug.aspx?PostID=407" width="1" height="1"&gt;</description></item></channel></rss>