14. Model Model represents the business domain which includes the model classes used (Customer, Order, etc.), data access code and business rules. 7 http:/facebook/honeydev
15. View Viewin MVVM represents the screens that we build. Includes : 1.XAML files 2.code-beside files Responsibilities : 1.displaying data 2.collecting data from end users View isn't responsible for retrieving data, performing any business rules or validating data 8 http:/facebook/honeydev
16. ViewModel ViewModel acts as middle-man between View and Model Responsibilities : Aggregating and storing data that will be bound to a View 9 http:/facebook/honeydev
19. Helpers around MVVM…cont View might need to notify the ViewModelabout something happened in the View. eg: a control being clicked. ViewModelneed to notify to the View when something happen. For these we use Events, another good way is to use Messages. 11 http:/facebook/honeydev
23. ViewModelBase. Also 1. EventToCommandwhich can be used to get rid of annoying WPF and SL Command binding limitations. 2. DispatcherHelperfor multi-threaded applications. 12 http:/facebook/honeydev
24. For Example Step 1 VIEW Button Base.Command connects view with ViewModel (GetPersonreturntype is Icommand—comand object)- following Commn design pattern VIEW Model PersonViewModelcontructor connects to PersonModel 13 http:/facebook/honeydev
25. Model Property changed event results in UI updates – from context (two way binding) 14 http:/facebook/honeydev