Should i add mvvm framework to an old project

Asked Sep 20 '16 at 10:05

Active Sep 20 '16 at 10:05

Viewed 62 times

I'm adding a window to an old project. (10 years+ age) should i make the window consistent with the other old windows or create the new page MVVM style?

There are some bad attempts at MVVM already in the project. Along with some attempts at resource dictionaries ect.

My worry is making an MVVM window that makes it harder for the other devs. The last time i asked this I was greeted with both positive and negative responses from other devs on the project.

what are some solid positives for making it MVVM so i can put the points across to any nay sayers?

asked Sep 20 '16 at 10:05

Sam

Is the SOC where someone else would design the View? – paparazzo Sep 20 '16 at 10:55
1

sorry im a little unsure what you mean by that – Sam Sep 20 '16 at 11:02
Then you are going to have trouble selling this to other devs. – paparazzo Sep 20 '16 at 11:06
see [this post](http://stackoverflow.com/questions/1644453/why-mvvm-and-what-are-its-core-benefits) for benefits of mvvm – vkluge Sep 20 '16 at 12:12
Whichever is better. – Sep 20 '16 at 16:36

Should i add mvvm framework to an old project

0 Answers0