A stackoverflow search will result in several postings that contain similar titles, but this is different question. Since this is not a discussion site, I have to ask a different question.
What unique benefits do I get from using MVVM that I can not get from any other implementations? MVC. NTiers, or anything else. Im not really looking for the identifying features that make MVVM different. Im looking for the things that can not be done in anything else but MVVM. My current knowledge on it leads me to think, that MVVM is different way to do the same thing that introduces more complexity then say nTiers. I dont want to take the angle that the introduction of this complexity , is a negative thing. If it is justified by the enabling of unique benefits then I would like to know this.
An in depth google, has only turned up MVVM defenitions. It has not turned up these unique benefits.
MVVM is just a tiny twist on a the class “Model-View-Presenter” pattern. The only diff with MVVM is that your ‘view-model’ classes are designed specifically to play nicely with the databinding features that are built in to WPF and Silverlight in order to minimize the need for any code in the View itself (keeping the View purely XAML markup that can be edited/replaced in a designer). If you are using WPF or Silverlight, it’s definitely worth a close look. If you are using anything else, it’s not really applicable.