Get flash to fully experience Pearltrees
While I’m not a zealot on the topic, I do believe that MVVM offers one of the best patterns for Windows Phone development and so, moving forward, the W indows P hone F rom S cratch series will incorporate MVVM in general, and the MVVM Light Toolkit in particular. I’m more than convinced that MVVM is an essential pattern for Windows Phone Development; and while there are many excellent frameworks to make MVVM development easier, the one I personally prefer to work with is the MVVM Light Toolkit and so it is the one I’ll focus on.
This is the second part of the MVVM Light Toollkit Soup To Nuts (part 1 is here ) within the Windows Phone From Scratch Mini-tutorial series. Today we look at an introduction to behaviors as a tool for migrating event handling from code-behind to the View-Model. Behaviors were originally introduced in Blend to empower designers, but they turn out to be enormously helpful to C# programmers as well. For example, it is a design goal to move as much of the (testable) logic of the program out of code-behind (where testing is more difficult) and into the View-Model. But what to do about events, such as the click event on a button?
This is the third part of the MVVM Light Toollkit Soup To Nuts (part 1 is here ) within the Windows Phone From Scratch Mini-tutorial series. Today we look at an introduction to messaging as a tool for communicating, e.g., from the view-model to the view. What We’ll Build To illustrate this, we’ll return to the example we began in part 1, and extended in part 2 (you can download the part 2 source code here ).
Let’s back up a bit and examine the day to day use of a View Model, and binding to the view model. In this mini-tutorial I’ll show the basics of binding a collection that sits in a View Model to a list box in the view.
Windows Phone From Scratch #20 MVVM Light Toolkit Soup To Nuts #5 In the previous posting in this series, we created a list of customers and we bound them to a list box.