Answered by:
MVVM and Non-MVVM

Question
-
Hi developer,
I heard about MVVM and i know what it is but i am mostly using without mvvvm.
I need to know what is difference between mvvm and non-mvvm in WPF?
Thanks
Sunday, August 2, 2015 6:06 PM
Answers
-
One important difference is that almost every team and every developer uses MVVM.
If you don't, then getting a new job using wpf is going to be tough.
They use mvvm because it's a better way to work.
.
MVVM separates out code from the view so it can be worked on separately, tested separately and gain the usual benefits from separation of concerns.
This is a recent pretty similar thread:
- Marked as answer by IamGuy84 Tuesday, August 4, 2015 4:43 AM
Sunday, August 2, 2015 6:56 PM
All replies
-
MVVM is a design pattern whose intent is to help you providing a clean separation of concerns between the user interface controls and their logic. One of the benefits this pattern brings is that you can test your application logic without the view, i.e. you run unit tests against the view model class only.
There are three core components in the MVVM pattern: the model, the view, and the view model. Each serves a distinct and separate role. Please refer to the following pages for more information about the MVVM pattern and how to implement it in WPF:
The MVVM Pattern: https://msdn.microsoft.com/en-us/library/hh848246.aspx
Implementing the MVVM Pattern Using the Prism Library 5.0 for WPF: https://msdn.microsoft.com/en-us/library/gg405484(v=pandp.40).aspx
Understanding the basics of MVVM design pattern: http://blogs.msdn.com/b/msgulfcommunity/archive/2013/03/13/understanding_2d00_the_2d00_basics_2d00_of_2d00_mvvm_2d00_design_2d00_pattern.aspxHope that helps.
Please remember to close your threads by marking helpful posts as answer and then start a new thread if you have a new question. Please don't ask several questions in the same thread.
Sunday, August 2, 2015 6:54 PM -
One important difference is that almost every team and every developer uses MVVM.
If you don't, then getting a new job using wpf is going to be tough.
They use mvvm because it's a better way to work.
.
MVVM separates out code from the view so it can be worked on separately, tested separately and gain the usual benefits from separation of concerns.
This is a recent pretty similar thread:
- Marked as answer by IamGuy84 Tuesday, August 4, 2015 4:43 AM
Sunday, August 2, 2015 6:56 PM -
Thanks for info. I will have a lot to learn about MVVM.Tuesday, August 4, 2015 4:44 AM