What is your experience with abandoning MVVM for UserControl-based WPF architecture?

Question

We built an large application based on Composite Application Library and MVVM using Infragistics controls.

In orde

Answer 1

Advocates of MVVM over state their case. They claim that the alternate to MVVM is necessarily spaghetti code. What Edward describes is still following a pattern, it's just not MVVM. The fact that Views bind to Models is similar to MVC. The code behind can be considered the controller.

Clearly, he feels the results are better in terms of development effort AND maintainability. Since the latter is the only valid rationale for a design pattern, the case against his approach isn't clear.

Saying "you don't understand MVVM" isn't really an argument against his approach. A pattern that is easier to understand is better than one that isn't.