Model-View-ViewModel (MVVM) is THE most successful UI development paradigm ever … measured by the number and variety of people talking about it. I don’t recall anything like this level of interest with respect to MVP or MVC. For most of UI history the majority of developers couldn’t name the pattern they were using … if they even thought they had a pattern. “MVC”, for most people, is a technology, not a design pattern.
Today, MVVM is the jargon-du-jour. And I think that’s a good thing.
We should retain some perspective. Not every view must be MVVM. And yet a healthy number of WPF/Silverlight screens should be done in MVVM style and I’d want to have a really good reason to depart from that standard.
How do you write a screen in MVVM style? Do you need a framework?
Some people think you do. There are plenty to choose from. And Laurent Bugnion’s “MVVM Light” has to be the most popular of the ulta-lightweight choices.
One of our customers asked for an example of DevForce and Mvvm Light working together. I put such an example together and made it available on the “DevForce Resource Center” (DRC); the Mvvm Light example page is here.
I provide code that shows three ways to start a DevForce + Mvvm Light application and one “Hello World” example.
Blend is a critical part of the story. “Blendability” is central to the Mvvm Light philosophy … and I agree. The working example view was written entirely in Blend.
Expect more from me soon on developing with Blend.
Meanwhile, here’s your launch point for Mvvm Light with DevForce.