0

this is a newbie question for wpf. Are ViewModels in wpf useful. Theres a drive where i work to convert all our controls to follow the MVVM architecture to create viewmodels. I dont really grasp or understand why it is useful to spend time refactoring code creating viewmodels...so I am asking you guys if it is worth it. Basically, what is the use of this mvvm architecture?

Ok, I know that I should do a google search, but I am a starting level programmer for wpf, so when I read articles on google about MVVM, it gives me a conceptual idea of why thats important but Im afraid I dont fully understand the concept from a practical standpoint I guess... Thanks

user1202434
  • 2,243
  • 4
  • 36
  • 53
  • sounds a little open and better suited programmers exchange – Jodrell Apr 17 '12 at 14:29
  • Search for "why mvvm" in your favorite search engine, or on StackOverflow http://stackoverflow.com/search?q=why+mvvm – Jay Apr 17 '12 at 14:30
  • there are lots of articles out there already http://msdn.microsoft.com/en-us/magazine/dd419663.aspx for instance – Jodrell Apr 17 '12 at 14:31
  • possible duplicate of [Why use MVVM?](http://stackoverflow.com/questions/2653096/why-use-mvvm) – Jay Apr 17 '12 at 14:32
  • @Jodrell - nope. Not suitable (in it's present form) for Programmers. Too open and not constructive. – ChrisF Apr 17 '12 at 14:32

1 Answers1

2

MVVM is not neccessary, but it helps a lot if your application gets more complex and when you want a clean separation between the view and application logic.

I would recommend you to use MVVM unless your application is very simple.

thumbmunkeys
  • 20,606
  • 8
  • 62
  • 110