Mvvm pattern
- 1. MVVM PatternMahenderSenior Software EngineerUnited Health Group
- 2. Mahender SarangamHaving 5 years of experience on .NET Technologies. Working as a Senior Software Engineer in United Health Group (UHG India Information Service Ltd.). Worked with Big Firms like Deloitte Consulting & Wipro Technology. Got Technical Acquaintance on Technologies like C#, ASP.NET,AJAX, LINQ, Silverlight, WPF,WCF ,SQL Server, Team Foundation Server(TFS) and SharePoint Technology. MCTS Certified in Web Technologies.Blog : http://Msarangam.wordpress.com
- 3. Why Do need PatternEverything in code behind, is not a good idea
- 5. Why Do need PatternBasic Motivation of separation patternRemoving logic from Code behindInterchanging UI screensCreate Unit test case foe logic and UIDevelopers and Designers can work parallel.Model never needs to be changed to support changes to the viewNo duplicated code to update viewsSo what is MVVM ?Its variation of MVC patternJohn Gossman from WPF team Resources from external assembliesMartin Fowler's Presentation Model (PM) pattern
- 7. MVC & MVP Difference
- 9. DiagramView Knows VIEW MODELVIEW MODEL Knows MODELBUT VIEWMODEL does not know ViewViewView ModelModel
- 10. ViewRepresents the user interface that the user will see.
- 11. Can be a user control or Data Template
- 12. Keep the view as simple as possible.Uses Binding to “subscribe” to the ViewModelInterprets business data and state of ViewModel to the humanNothing but Presentation - XAMLNo or minimal code-behind
- 13. View ModelAn abstraction of View
- 14. Connector between View and Model
- 15. Keep View State, Value Conversion
- 16. No strong or weak (via Interface) reference of View
- 17. Make VM as testable as possible (e.g. no call to Singleton class)
- 18. No Control related Stuff in VMProvides data to and from the ViewResponds to both the View and the ModelInforms the View of changes in the dataReusable (at least much more than code behind a form)
- 19. ModelCan 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
- 20. No reference to View ModelTypical class that covers a databaseCould be a WCF Service and its client reference
- 21. SupportingLibraires and FrameworkWPF Team : MVVM Toolkit
- 22. MS Pattern and Practice Team : Composite WPF (Prism)
- 23. Josh Smith. "MVVM Foundation"
- 26. Laurent Bugnion. "MVVM Light Toolkit"
- 29. William e Kempf. "Onyx"
- 31. jbe. "WPF Application Framework (WAF)"
- 32. Paul Stovel : MacroModels Thank you