The document discusses Model-View-ViewModel (MVVM) as an architectural pattern for building user interfaces. It describes some issues with traditional MVC/MVP approaches and introduces MVVM as a more testable alternative that separates the model and view using a view model layer. The document then evaluates different implementations of MVVM, highlighting features like messaging, commanding, and dependency injection provided by frameworks like Caliburn.Micro to help realize the MVVM pattern. It concludes by asking if the audience has any other questions.

1. WP7 + MVVM
William Brander
@WilliamBZA
http://www.WilliamB.Net
william@williamb.net

2. Design Patterns like a baws
Model View
Controller

3. MVC/P is cool, but…
• What about separate model
objects?
• How do objects
communicate?
• Hard to test – tightly coupled!

4. Naïve MVVM
Model
ViewModel View
Model Controller

5. Cool. Or is it?
• More testable
• Can combine multiple objects into
one
• But all we’ve done is aggregate our
model

6. A Better MVVM
View
DataBinding
Commands
Messaging
ViewModel Controller
Models

7. Caliburn.Micro
• Dependency Injection
• Messaging
• Commanding

8. MVVM Frameworks
• Roll your own
• Caliburn.Micro
• MVVM Light
• Atomic MVVM

9. Questions?
William Brander
@WilliamBZA
http://www.WilliamB.Net
william@williamb.net