Menu
I have been hearing a lot of hype about MVVM for WPF.
When do we use it?
Is it a use for everything or does it only have specific uses?
Is it worth it for every project?
693
MVVM is enough for small projects, but when your codebase becomes huge, your ViewModel s start bloating. Separating responsibilities becomes hard. MVVM with Clean Architecture is pretty good in such cases. It goes one step further in separating the responsibilities of your code base.
The pattern is often used in Windows and web graphics presentation software. The MVVM pattern is used in Windows Presentation Foundation (WPF), which runs on Microsoft's . NET. Silverlight, a Microsoft WPF internet equivalent multimedia plug-in, also uses MVVM.
MVVM separates the different components of the development process into three categories, model, view and ViewModel. This typically involves code markup or graphical user interfaces (GUI). MVC, or model-view-control is a way developers separate programs into these three components.
MVC patterns are found in popular frameworks such as Rails, Django, and CakePHP, while MVVM patterns are found in Silverlight, nRoute, Caliburn, and WPF.
It can be useful in any project, but I find it particularly helpful in situations where providing a clear separation between business logic, interaction logic, and user interface is required (large applications or applications involving multiple developers/designers).
Model = Business Logic
ViewModel = Interaction Logic
View = User Interface
There are doubtless many other uses for MVVM, but this particular scenario is the one I have found to be the most useful in my own WPF development experience.
117
I've found it useful even in relatively small projects, if I'm making a lot of use of databinding and an object data model / models.
38
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
