Introduction to the Model-View-ViewModel Pattern for WPF and Silverlight
By: Dave Kehring

The Model-View-ViewModel pattern (MVVM) is emerging as the architectural pattern of choice when composing non-trivial WPF and Silverlight applications. MVVM, a specialized variant of the tried and true MVC pattern, provides for clear separation between UI and application logic that is traditionally mixed in Win Forms and WPF code-behind. This separation allows us to:

• Apply automated unit testing to application logic
• Better separate developer and designer roles
• Reuse application logic between different "views"
• Change the UI components without changing application logic

• Why you should use the pattern
• How to connect views, models and viewmodels
• Unit testing of viewmodels
• How to work with collections of objects in a view
• Code-behind is bad
• Commands
• Message and dialog boxes
• Replacing the hourglass cursor
• Using dependency injection for viewmodels
• Active models

About Dave Kehring - Dave Kehring is an independent consultant, developer and software architect with 22+ years of experience. His company White Horse Consulting Inc. builds software solutions for large and small companies in a variety of industries including financial services, oil and gas, business simulation, semi-conductor, manufacturing and health care.