MVVM standardization

Question

Someone in Silverlight posted that MVVM currently lacks standardization so that everyone has own flavor..

That\'s why me and a few guys from WPF Disciples are actively

Answer 1

I like what you have written. One of the things that really bugs me is that a lot of people seem to have their VM coupled very tightly to their View - if you are doing this then you might as well just be doing the old XAML + everything whacked into the code behind thing.

The pattern I use is a slight variant on the MVVM (but it is mostly the same). Personally I like to have my ViewModel given to the View as an interface - it keeps the separation very clean. This has a lot of benefit when doing prototypes, visual elements can be switched in or out of the View with little or no impact on the ViewModel.