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 think the communication between View ViewModel via databinding is what makes MVVM it's own pattern as opposed to other separation of concerns. It isn't so much whether it whether its GOOD or BAD for the vm to know about the view via interface, but in the context of communicating the pattern being used it is not MVVM.

Some of the difficulty in getting and maintaining standards lies in the shortcomings and complexity of WPF and Silverlight, sadly. When there are multiple valid standards however, I would put on my Martin Fowler hat and add a "when to use it" section.

Do your standards cover cross-cutting concerns like localization?

FWIW I like the content of what you wrote and am glad you posted it here...

Cheers,
Berryl