Pro Business Applications with Silverlight 5

MVVM Theory

At the heart of the MVVM design pattern is the separation of a view's logic from its look. Instead of having a mass of code in a View's code-behind, much of this code will be extracted out into a ViewModel class—separated from the View itself. This ViewModel class will then expose data and operations publicly for one or more Views to consume. The result of this will be that the view should have very little code-behind. You can then use data bindings and commands/behaviors as the glue to connect the View and the ViewModel together.

Let's take a look at the theory behind the MVVM design pattern and how you can put these principles in place in your Silverlight business applications.

The Layers

The MVVM design pattern consists of three ...