The Model-View-ViewModel pattern is similar to the Model-View-Presenter, except you have a model tailor-made for the View, called the ViewModel. The ViewModel contains all the UI-specific interfaces and properties necessary to make it easy to develop a user interface. The View binds to the ViewModel, and executes commands to request an action from it. The ViewModel, in turn, communicates with the Model, and tells it to update in response to user interaction.
Model-View-ViewModel Example
- A model that contains the data
-
A passive view-model that collects and prepares the data so that is an easy be consumed by the view.
-
view that is defined in XAML and should not have any logic in the code-behind. It binds to the view-model by only using data binding.
Read on...
http://msdn.microsoft.com/en-us/magazine/dd419663.aspx