MVVM
Get flash to fully experience Pearltrees
Last week, I’ve posted two series of my blog post on our upcoming ClientUI for Silverlight and WPF 4. The first series discussed about architectural overview while the second series discussed more deeply on the presentation model and the control’s development standards compliance. I highly recommend you to check them out if you haven’t done so. The recent rising of the MVVM design pattern has created a fairly strong buzz around the community, developers and .NET shops who build RIA applications specifically for the Silverlight platform. If you’re just about getting into MVVM and stucked with conceptual difficulties and technical challenges – you’re not alone.
ClientUI Part 3 – Comprehensive MVVM Framework for Silverlight Development | Intersoft Solutions Corporate Blog
C#er : IMage: Model-View-ViewModel (MVVM) Explained
The purpose of this post is to provide an introduction to the Model-View-ViewModel (MVVM) pattern. While I've participated in lots of discussions online about MVVM, it occurred to me that beginners who are learning the pattern have very little to go on and a lot of conflicting resources to wade through in order to try to implement it in their own code. I am not trying to introduce dogma but wanted to pull together key concepts in a single post to make it easy and straightforward to understand the value of the pattern and how it can be implemented. MVVM is really far simpler than people make it out to be.
WPF patterns : MVC, MVP or MVVM or…? :: Orbifold
Introduction Since XAML things have become a bit complicated in trying to conceptualize MVC architectures for Windows applications. The gap between web and win is narrowing and the whole WPF thing adds diverse possibilities to one's toobox. What to use? Model-view-controler, the model-view-presenter or the new paradigm called model-view-viewmodel? I have tried to understand what it's all about and this is what I found out.
Patterns WPF Apps With The Model-View-ViewModel Design Pattern Josh Smith
THE MODEL-VIEW-VIEWMODEL (MVVM) DESIGN PATTERN FOR WPF
Fundamental MVVM
Papa's Perspective Fundamental MVVM Understanding Model-View-ViewModel is the first step in using it. By John Papa 08/15/2011
For the consicise explanation, see MVVM vs MVP vs MVC: The concise explanation Those who know me know that I have a passion for software architecture and after developing projects using Model-View-ViewModel (MVVM), Model-View-Presenter (MVP), and Model-View-Controller (MVC), I finally feel qualified to talk about the differences between these architectures. The goal of this article is to clearly explain the differences between these 3 architectures.
Joel in point form » MVVM vs MVP vs MVC: The differences explained » Joel
In my own learning of WPF or any technology that I learn, I use the same approach and design principles that I would for a technology I know inside out. I have used winforms for years and I would be modest to say I know how to design a winform application the right way. It would be the approach I would use if I was developing an application in java swing. I would at the forefront of my design use the “model view controller” (MVC) pattern. The MVC pattern has been around since I was born and has been discussed and debated to death over the years. MVC aside I would use a number of other design patterns that fit the bill for concern situations.
Overview of the ModelView – ViewModel (MVVM) pattern and data-binding « Russell East’s blog
An important FAQ. The answer actually depends on where the person is coming from. MVC is a fundamental pattern which has been tweaked quite a bit to fit into various platforms. For instance if you had asked anybody how to implement an MVC in ASP.NET (prior to release of ASP.NET MVC framework) you would get very different answers. So let’s start with basic.