1 / 11

WPF MVVM Training

WPF MVVM Training. Michael Sync (Silverlight MVP). Adopting the MVVM pattern with WPF. Understanding MVVM Motivation and benefits Implementing the pattern Dependency Injection and IoC Unit Test and Mock Supporting libraries and frameworks. What's MVVM?.

eleanor-turner
Download Presentation

WPF MVVM Training

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WPF MVVM Training Michael Sync (Silverlight MVP)

  2. Adopting the MVVM pattern with WPF • Understanding MVVM • Motivation and benefits • Implementing the pattern • Dependency Injection and IoC • Unit Test and Mock • Supporting libraries and frameworks

  3. What's MVVM? • is an architectural pattern created by John Gossman from WPF team • is a variation of MVC pattern • is similar to Martin Fowler’s PresentationModel pattern • WPF Data Binding & Commanding

  4. Motivation and benefits • Testabiltiy ( ViewModelis easier to unit test than code-behind or event driven code) • Clearseperationbetween UX designer and developer • Increases the "Blendability" of your view • Model never needs to be changed to support changes to the view • ViewModel rarely needs to be changed to support changes to the view • No duplicated code to update views

  5. MVVM • View knows ViewModel • ViewModelknows Models • But not vice versa. View ViewModel Model

  6. View • represents the user interface that the user will see. • can be a user control or Data Template • shouldn't contain any logic that you want to test • Keep the view as simple as possible.

  7. View Model • An abstraction of View • Connector between View and Model • Keep View State, Value Conversion • No strong or weak (via Interface) reference of View • Make VM as testable as possible (e.g. no call to Singleton class) • No Control related Stuff in VM

  8. Model • can be Data Model, DTO, POCO, auto-generated proxy of domain class and UI Model based on how you want to have the separation between Domain Service and Presentation Layer • No reference to ViewModel

  9. Disadvantages of MVVM • lack of standardization so everyone has own favor • For simple UI, M-V-VM can be overkill

  10. Implementing MVVM • DEMO – Simple MVVM • DEMO – MVVM + Data Template • DEMO – DI + IoC • DEMO – BDD

  11. Supporting libraries and frameworks • WPF Team : MVVM Toolkit • MS Pattern and Practice Team : Composite WPF (Prism) • Josh Smith. "MVVM Foundation" • Sacha Barber. "Cinch." • Karl Shifflett. "Ocean" • Laurent Bugnion. "MVVM Light Toolkit" • Lester Lobo. "CoreMVVM" • Rob Eisenberg. "Caliburn" • William e Kempf. "Onyx" • Peter O’Hanlon. "GoldLight" • jbe. "WPF Application Framework (WAF)" • Paul Stovel : MacroModels

More Related