<?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 - Implementing an MVVM MessageBus with XAML</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/posts/Implementing-an-MVVM-MessageBus-with-XAML/rss"></atom:link>
	<image>
		<url>http://ak.channel9.msdn.com/ch9/0B9C/E18FB33C-EA1C-4242-918C-9E7100D50B9C/XamlMessageBus_100_ch9.jpg</url>
		<title>Channel 9 - Implementing an MVVM MessageBus with XAML</title>
		<link></link>
	</image>
	<description> Using a Messag Bus to communicate between ViewModels is a very common activity when building an application based on MVVM.&amp;nbsp; In this video, I show how you can build a Message Bus that can be created on a per-page basis and easily connected to the ViewModels on a page using XAML. For&amp;nbsp;a deeper written explanation of this approach, and to download the source code for the project seen in the video, check out my blog post on Slickthought.net. &amp;nbsp; </description>
	<link></link>
	<language>en</language>
	<pubDate>Fri, 24 May 2013 10:22:18 GMT</pubDate>
	<lastBuildDate>Fri, 24 May 2013 10:22:18 GMT</lastBuildDate>
	<generator>Rev9</generator>
	<item>
		<title>Re: Implementing an MVVM MessageBus with XAML</title>
		<description>
			<![CDATA[ <p>Just so everyone is not having to change the xaml in Blend. When you add a object data source it asks you for the key of the object at the top of the dialog window.</p><p>posted by Scptrez</p>]]>
		</description>
		<link>http://channel9.msdn.com/posts/Implementing-an-MVVM-MessageBus-with-XAML#c634312344220000000</link>
		<pubDate>Fri, 21 Jan 2011 19:20:22 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/posts/Implementing-an-MVVM-MessageBus-with-XAML#c634312344220000000</guid>
		<dc:creator>Scptrez</dc:creator>
	</item>
	<item>
		<title>Re: Implementing an MVVM MessageBus with XAML</title>
		<description>
			<![CDATA[Any reason you are not using event aggregators provided by prism?<p>posted by Ganesh</p>]]>
		</description>
		<link>http://channel9.msdn.com/posts/Implementing-an-MVVM-MessageBus-with-XAML#c634315410740000000</link>
		<pubDate>Tue, 25 Jan 2011 08:31:14 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/posts/Implementing-an-MVVM-MessageBus-with-XAML#c634315410740000000</guid>
		<dc:creator>Ganesh</dc:creator>
	</item>
	<item>
		<title>Re: Implementing an MVVM MessageBus with XAML</title>
		<description>
			<![CDATA[ <p>@<a href="/posts/Implementing-an-MVVM-MessageBus-with-XAML#c634315410740000000">Ganesh</a>: Not really.&nbsp; This was more of an effort to illustrate different ways to incorporate XAML and design-time support rather than deal with event routing /messaging per se.&nbsp; PRISM is great, but for a lot of apps it is also overkill so this was just a nice, simple way to get some of the goodness provided by things like Event Aggregator without having to dive into PRISM.</p><p>posted by SlickThought</p>]]>
		</description>
		<link>http://channel9.msdn.com/posts/Implementing-an-MVVM-MessageBus-with-XAML#c634315694320000000</link>
		<pubDate>Tue, 25 Jan 2011 16:23:52 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/posts/Implementing-an-MVVM-MessageBus-with-XAML#c634315694320000000</guid>
		<dc:creator>SlickThought</dc:creator>
	</item>
</channel>
</rss>