Is Model-View-ViewModel the best pattern to use in WPF? Are there any downsides?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is Model-View-ViewModel the best pattern to use in WPF? Are there any downsides?
Here’s a good, short blog post on the advantages and disadvantages of MVVM, straight from John Gossman (*) himself.
His main disadvantages are:
"For simple UI, M-V-VM can be overkill. In bigger cases, it can be hard to design the ViewModel up front in order to get the right amount of generality. Data-binding for all its wonders is declarative and harder to debug than nice imperative stuff where you just set breakpoints"