In this article we explain just how simple it can be to build a WPF application the right way using the MVVM Pattern.
MSDN Magazine February 2009
View Complete Post
The Model-View-ViewModel (MVVM) design pattern describes a popular approach for building Windows Presentation Foundation or Microsoft Silverlight applications. Robert McCarter shows you how the ViewModel works, and discuss some benefits and issues involved in implementing a ViewModel in your code.
MSDN Magazine July 2010
In this article, you'll learn how to avoid problematic tight coupling by applying the Model-View-ViewModel pattern in Silverlight 2.
MSDN Magazine March 2009
The MVP pattern helps you separate your logic and keep your UI layer free of clutter. This month learn how.
MSDN Magazine August 2006
Service-oriented architecture is a great framework when you need to perform distributed computing tasks over the Internet. But when you want to perform processing inside your local network, a different solution may provide a better fit. That solution, based on the Command pattern, uses Windows services and Microsoft Message Queuing to implement a queued system that meets your needs better than a service-oriented solution. This article explains how to build it.
MSDN Magazine September 2004
MSDN Magazine December 2003
I´m playing around with XAML and MVVM, and have a question about the wiring between the model and the viewmodel:
If I have a model that updates its data on random times, what wiring is used between the model and the viewmodel to let the viewmodel know that the model has changed?.
Between the view and viewmodel a bindings and NotifyPropertyChanged would take care of this.
I have model called Car with prperties name,model,type,year.
I have implemeted the Viewmodel with same properties with OnpropertyChangedEvent including model object type Property.
I have a view usercontrol where textboxes for name, model and for year a combobox.
Whenever i fill the view i want to save those details into model via view model
I have written ICommand Save which calls SaveCarDetails defined in viewmodel, which is bind to a button in view ,All other texboxes text is bind to the properties of viewmodel properties.
When i put break point at ICommand SaveCommand and SaveCarDetails Function i could see the values filled from view.
But when i bind these details to another user control where listbox is placed and its itemsource property is set to Car property nothing but model object defined in the viewmodel.
I couldn't see the values binding via viewmodel to model.
Where as if i bind to textboxes in the listview i could see the values because i it's a dependency property.
Can any one please tell me what is the wrong i am doing here.