<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>DataModel-View-ViewModel pattern: 1</title><link>http://blogs.msdn.com/dancre/archive/2006/07/23/datamodel-view-viewmodel-pattern-1.aspx</link><description>John Gossman has blogged several times about the M-V-VM pattern for developing WPF applications. We've been using a similar pattern on the Max team, with slightly different terminology (DataModel instead of ViewModel). I thought I'd do a series of posts</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: DataModel-View-ViewModel pattern: 1</title><link>http://blogs.msdn.com/dancre/archive/2006/07/23/datamodel-view-viewmodel-pattern-1.aspx#676927</link><pubDate>Mon, 24 Jul 2006 20:48:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:676927</guid><dc:creator>Joe</dc:creator><description>Trying to understand your distinction between VM and DM. &amp;nbsp;Is it right to say that a DataModel holds the data (or wraps the data) but the ViewModel holds view specific state like sort order, filtering etc...?&lt;br&gt;In some cases you don't need a ViewModel because WPF provides it for you (DataTemplates etc..)&lt;br&gt;&lt;br&gt;If this is right then isn't your ViewModel the same as John Gossman's? &amp;nbsp;The only difference is that you have a DataModel and he has a plain Model.</description></item><item><title>re: DataModel-View-ViewModel pattern: 1</title><link>http://blogs.msdn.com/dancre/archive/2006/07/23/datamodel-view-viewmodel-pattern-1.aspx#677273</link><pubDate>Tue, 25 Jul 2006 02:22:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:677273</guid><dc:creator>dancre</dc:creator><description>A ViewModel is a bit more than that. It basically contains all of the behavior for a view and the view will have no codebehind. I hope it will become more clear as I build up an example. One of the key things is that it exposes things like commands and may aggregate several different DataModels.</description></item><item><title>Hello Tuesday</title><link>http://blogs.msdn.com/dancre/archive/2006/07/23/datamodel-view-viewmodel-pattern-1.aspx#678411</link><pubDate>Wed, 26 Jul 2006 03:50:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:678411</guid><dc:creator>Okoboji: a lake, a mythical university, Kevin Moore's blog</dc:creator><description>Control Licensing in Cider (WPF designer for VS)
James provides some
great 
information on supporting...</description></item><item><title>WPF Patterns</title><link>http://blogs.msdn.com/dancre/archive/2006/07/23/datamodel-view-viewmodel-pattern-1.aspx#774333</link><pubDate>Wed, 27 Sep 2006 23:31:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:774333</guid><dc:creator>Bryant Likes's Blog</dc:creator><description>If you're doing WPF development, you really need to check out Dan Crevier 's series on DataModel-View-ViewModel.</description></item><item><title>DataModel-View-ViewModel pattern series</title><link>http://blogs.msdn.com/dancre/archive/2006/07/23/datamodel-view-viewmodel-pattern-1.aspx#818055</link><pubDate>Thu, 12 Oct 2006 05:00:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:818055</guid><dc:creator>Dan Crevier's Blog</dc:creator><description>&lt;p&gt;I thought I should add a post with the full list of posts in the D-V-VM pattern. They are: DataModel-View-ViewModel&lt;/p&gt;
</description></item><item><title>re: DataModel-View-ViewModel pattern: 1</title><link>http://blogs.msdn.com/dancre/archive/2006/07/23/datamodel-view-viewmodel-pattern-1.aspx#819495</link><pubDate>Thu, 12 Oct 2006 15:57:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:819495</guid><dc:creator>Udi Dahan - The Software Simplist</dc:creator><description>&lt;p&gt;By this:&lt;/p&gt;
&lt;p&gt;&amp;quot;When data is expensive to fetch, it abstracts away the expensive operations, never blocking the UI thread (that is evil!). It also keeps the data &amp;quot;live&amp;quot; and can be used to combine data from multiple sources.&amp;quot;&lt;/p&gt;
&lt;p&gt;Do you mean that the data model is also responsible for when to communicate out? If so, I'd say that you're violating the Single Responsibility Principle. &lt;/p&gt;</description></item><item><title>re: DataModel-View-ViewModel pattern: 1</title><link>http://blogs.msdn.com/dancre/archive/2006/07/23/datamodel-view-viewmodel-pattern-1.aspx#819817</link><pubDate>Thu, 12 Oct 2006 18:20:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:819817</guid><dc:creator>dancre</dc:creator><description>&lt;p&gt;See part 6 for the activation model.&lt;/p&gt;
</description></item></channel></rss>