Share the Love	Get Free Updates
Tweet

I came across a couple of different ways to implement MVVM that I would like to share here

1. I have seen applications where M V VM is completely implemented on the client’s side meaning for example,
   
   • View is the UI with Xaml and code behind, Model which stores the data, ViewModel implements INotificationPropertyChanged event and is a bridge between View and the Model and talks to a WCF service for example this is what ‘John Papa’ has to say…
     http://johnpapa.net/5-Minute-Overview-of-MVVM-in-Silverlight
   • View is the UI with Xaml and code behind, Model which stores the data and talks to a WCF service, and ViewModel implements INotificationPropertyChanged event and is a bridge between View and the Model for example this is what Song Li has to say…
     http://www.codeproject.com/KB/WPF/MVVMQuickTutorial.aspx
     
2. In my work environment we have developed Silverlight applications where we followed MVVM Pattern more like how ‘Maria Veronica Evert Riveros’ has explained here http://mariaevert.dk/thesis/?p=577 but View and the ViewModel both resided in the same project rather than them being in different projects and the Model was the WCF Web Service where ViewModel communicates with the Model via a proxy.

I will try sharing more ways to play with MVVM as I stumble upon

Incoming search terms:

• xaml mvvm wcf example
• mvvm webservice
• wcf model or viewmodel
• wcf mvvm
• wcf silverlight mvvm
• wcf viewmodel
• wpf wcf mvvm example
• wpf and wcf viewmodel and model example
• silverlight mvvm project sample
• wpf wcf mvvm sample

Tagged as: INotificationPropertyChanged, M-V-VM, Model, Model View, Model View View Model, Model View ViewModel, MVVM, MVVM Pattern, Silverlight, View, ViewModel, WCF, Xaml