<?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 - Message Based Navigation for WP7 MVVM Apps</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/posts/Message-Based-Navigation-for-WP7-MVVM-Apps/rss"></atom:link>
	<image>
		<url>http://ak.channel9.msdn.com/ch9/d38f/c816a2d3-7b70-44bd-a91f-9ed00178d38f/MVVMNav_100_ch9.jpg</url>
		<title>Channel 9 - Message Based Navigation for WP7 MVVM Apps</title>
		<link></link>
	</image>
	<description> Do you have an MVVM-based Windows Phone 7 application and you don&#39;t like having to hook into the RootFrame to navigate between pages?&amp;nbsp; Do you wish you could just &amp;quot;ask&amp;quot; to navigate to a new view from your view model?&amp;nbsp;One possible solution can be found in this screencast. Using an message bus to process navigation messages, view models can publish messages that are then handled by a separate navigation service, successfully decoupling your view model from the Windows Phone navigation service.&amp;nbsp; Get the finished source code here </description>
	<link></link>
	<language>en</language>
	<pubDate>Wed, 22 May 2013 17:15:13 GMT</pubDate>
	<lastBuildDate>Wed, 22 May 2013 17:15:13 GMT</lastBuildDate>
	<generator>Rev9</generator>
	<item>
		<title>Re: Message Based Navigation for WP7 MVVM Apps</title>
		<description>
			<![CDATA[That seems like an awful lot of code and xaml spread out.<br><br>I solve this problem by having my VMs depend upon a IMyAppNavigationService that has methods such as<br>void NavigateToPersonView&#40;string id&#41;&#59;<br><br>That way all the URIs and navigation logic is in one class, the MyAppNavigationService. Even though message buses are cool I don&#39;t see the benefit here.<br><br>&#47;Linus<p>posted by Linus K</p>]]>
		</description>
		<link>http://channel9.msdn.com/posts/Message-Based-Navigation-for-WP7-MVVM-Apps#c634395858970000000</link>
		<pubDate>Thu, 28 Apr 2011 11:11:37 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/posts/Message-Based-Navigation-for-WP7-MVVM-Apps#c634395858970000000</guid>
		<dc:creator>Linus K</dc:creator>
	</item>
	<item>
		<title>Re: Message Based Navigation for WP7 MVVM Apps</title>
		<description>
			<![CDATA[ <p>I like to wire up XAML as much as I can.&nbsp; I don't think it is all that much code really... the MessageBus and NavigationHandler (which is the same thing as your IMyAppNavigationService) are very small.&nbsp; I replace the dependency you have on the nav service with a dependency on the message bus, which provides me additional capabilities.&nbsp; Too each there own... whatever works for the apps you build.&nbsp; Just thought it was an interesting alternative.</p><p>posted by SlickThought</p>]]>
		</description>
		<link>http://channel9.msdn.com/posts/Message-Based-Navigation-for-WP7-MVVM-Apps#c634395946270000000</link>
		<pubDate>Thu, 28 Apr 2011 13:37:07 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/posts/Message-Based-Navigation-for-WP7-MVVM-Apps#c634395946270000000</guid>
		<dc:creator>SlickThought</dc:creator>
	</item>
</channel>
</rss>