<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" media="screen" href="/styles/xslt/rss.xslt"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:c9="http://channel9.msdn.com">
<channel>
	<title>Comment Feed for Channel 9 - Prism &amp; Silverlight: Part 2 - Dependency Injection with Unity</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/Blogs/mtaulty/Prism--Silverlight-Part-2-Dependency-Injection-with-Unity/RSS"></atom:link>
	<image>
		<url>http://ecn.channel9.msdn.com/o9/previewImages/100/502095_100x75.jpg</url>
		<title>Channel 9 - Prism &amp; Silverlight: Part 2 - Dependency Injection with Unity</title>
		<link></link>
	</image>
	<description>
This is part&amp;nbsp;2 of a series of&amp;nbsp;screencasts illustrating&amp;nbsp;some of the ideas found in &amp;quot;Prism&amp;quot; or the &amp;quot;Composite
 Application Guidance&amp;quot; from the&amp;nbsp;Patterns and Practices team&amp;nbsp;that can be used to build Silverlight applications in a way that lends itself to testability and modularity.In talking to customers building business applications with Silverlight I find that Prism (and it&#39;s friend
Unity) is frequently mentioned but not everyone has seen it and so I thought I would explore it myself and capture some of the results of that exploration here.We start off with some fairly basic code which we move towards making use of dependency injection and modularity; 

Part 1: Taking Sketched Code&amp;nbsp;Towards Unity&amp;nbsp;
Part 2: Dependency Injection with Unity&amp;nbsp;
Part 3: Modularity with Prism&amp;nbsp;
Part 4: The Unity Bootstrapper&amp;nbsp;

and then we move&amp;nbsp;that code into the Silverlight world and try to illustrate some specific areas of Prism; 

Part 5: Moving to a Modular Silverlight Project&amp;nbsp;
Part 6: Shells, Regions, Views&amp;nbsp;
Part 7: Commands&amp;nbsp;
Part 8: Loosely Coupled Events with Event Aggregation
Part 9: Sharing Data via Region Contexts&amp;nbsp;

and then finally we try and bring some of these concepts together in a longer, more realistic example of a simple Email application built using the Prism framework - warning, this is a much longer session but I wanted something that draws things together; 

Part 10: A Larger Example: &amp;quot;Email Client&amp;quot;&amp;nbsp;

The recommendation would be that you watch the 10 screencasts in order but if that feels like too long a process or if you&#39;re already very familiar with concepts like dependency injection and containers like Unity then perhaps watch the last screencast first
 and then refer back to the previous screencasts if certain areas need more illumination.
I put the source code for Video 10&amp;nbsp;here for download as it&#39;s a bigger set of source and something you might want to explore after the video - this does not necessarily
 represent &amp;quot;best practise&amp;quot; but is, instead, just meant to illustrate some of the Prism ideas. 
</description>
	<link></link>
	<language>en</language>
	<pubDate>Thu, 23 May 2013 20:58:55 GMT</pubDate>
	<lastBuildDate>Thu, 23 May 2013 20:58:55 GMT</lastBuildDate>
	<generator>Rev9</generator>
	<item>
		<title>Re: Prism &amp; Silverlight: Part 2 - Dependency Injection with Unity</title>
		<description>
			<![CDATA[
<p>Excellent video but I'm having a problem with the app.config. I believe mine is correct but as soon as I remove the CalculatorLibrary reference, the InputOutputLibrary reference, or the CalculatorCommandParsingLibrary reference. I get a FileNotFoundException
 for the reference I remove. Any help would be appreciated. </p>
<p>Update: I realized that when my references were being deleted that they were deleting the dll's from the bin. All is good now.</p>
<p>posted by jmullany</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/mtaulty/Prism--Silverlight-Part-2-Dependency-Injection-with-Unity#c634062670880000000</link>
		<pubDate>Wed, 07 Apr 2010 19:58:08 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/mtaulty/Prism--Silverlight-Part-2-Dependency-Injection-with-Unity#c634062670880000000</guid>
		<dc:creator>jmullany</dc:creator>
	</item>
	<item>
		<title>Re: Prism &amp; Silverlight: Part 2 - Dependency Injection with Unity</title>
		<description>
			<![CDATA[
<p>I am sorry, I may be in the wrong place.&nbsp; I watched you turn one into five separate projects, for a add, mul, div, sub calculator.&nbsp; I need to know why I would do such a thing?</p>
<p>&nbsp;</p>
<p>If I have a sidebar with 10 - 12 categories, each responding with 20-100 choices, and all of this before I ever have to respond to the server, Why would I want to take a simple problem and make it complex?</p>
<p>&nbsp;</p>
<p>What I am looking for in Prism &quot;is a way to structure, a complex application with multiple origination points, as well as, multiple departure points.&nbsp; I am looking for a structure, that isolates individual functions (allowing a copy/replace to the web server
 without disrupting anyone), barring that I am looking to bring down independant/notify modules for replacement.</p>
<p>&nbsp;</p>
<p>If I understand &quot;Prism&quot;, I can loosely couple, and download mismatches.&nbsp; Is this correct?</p>
<p>&nbsp;</p>
<p>Ron</p>
<p>&nbsp;</p>
<p>P.S. A better blog would be to give us a real world application (search at every level, lists that bring up specific object type, comboboxes &nbsp;(with semi-static loading/cacheing), response to selection from a list (fills in source object and returns control),
 and a step through of the thought process, logic, and implementaion of your solution.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>posted by poppie</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/mtaulty/Prism--Silverlight-Part-2-Dependency-Injection-with-Unity#c634178532670000000</link>
		<pubDate>Thu, 19 Aug 2010 22:21:07 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/mtaulty/Prism--Silverlight-Part-2-Dependency-Injection-with-Unity#c634178532670000000</guid>
		<dc:creator>poppie</dc:creator>
	</item>
	<item>
		<title>Re: Prism &amp; Silverlight: Part 2 - Dependency Injection with Unity</title>
		<description>
			<![CDATA[ <p>Super video series thus far, really enjoying and learning a lot, thanks for sharing ;0)</p><p>posted by Philip_McKee</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/mtaulty/Prism--Silverlight-Part-2-Dependency-Injection-with-Unity#c634237210890000000</link>
		<pubDate>Tue, 26 Oct 2010 20:18:09 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/mtaulty/Prism--Silverlight-Part-2-Dependency-Injection-with-Unity#c634237210890000000</guid>
		<dc:creator>Philip_McKee</dc:creator>
	</item>
</channel>
</rss>