P&P Symposium 2010 - Model-View-ViewModel Pattern Primer - Karl Shifflett
- Posted: Nov 09, 2010 at 9:15 PM
- 4,575 Views
- 1 Comment
Model-View-ViewModel Pattern Primer | Karl Shifflett
The Model-View-ViewModel (M-V-VM) UI design pattern is a very natural fit for the Microsoft XAML platforms (WPF, Silverlight and Windows Phone 7) and is one of the most written and talked about topics in this space. This session will explain what M-V-VM is, why it is a natural fit for XAML platforms and its benefits to developers, designers and testers.
This session provides the foundation for the two following sessions that cover building M-V-VM applications.
Download the presentation materials from Karl's blog here.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
More posts in this blog
-
P&P Symposium 2010 - Agile Web Development with…
-
P&P Symposium 2010 - Model-View-ViewModel Pattern…
-
P&P Symposium 2010 - Windows Phone 7 Developer…
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
Good talk. How's "In the Box" coming along? Closer than Prism 4 release?
I like your point on "Breath, Crawl...". 5 long weeks of daily head exploding trying to learn the MVVM double digit concept count plus frameworks plus tools, to finally getting the full stack working. Lucky I had distractions.
A "seperation of learning MVVM concepts" information source would be handy. Learning View controls, then ViewModel with Commands and local properties is easy. People then move on to the Model where they should learn Unit Testing with DI, Interfaces and IoC as refactoring Repositories, business objects and the ORM is a pain after your just got your head around working the INotifyPropertyChange and IDataErrorInfo inheritence tree.
Remove this comment
Remove this thread
close