Why use an MVVM framework for WPF?

Question

Isn't writing the raw code to apply MVVM principles to a WPF project fairly straightforward? Why should I adopt a framework that adds 3rd-party dependencies to my project? Does anyone have any hands-on experience with this? After reading dozens of MVVM articles which all adopt a different approach and/or framework I'm finding it hard to decice how or even whether to adopt MVVM principles in a new project.

Selva Ganapathy · Answer

Hi Jez B Initially MVVM ( Model View ViewModel) is principle (actually a standard) is used to review the project easy and make the application light weighted. Also we cant feel any advantage while adopt the MVVM standard in a small application but the large one. While creating a real time application with a numerous entity its really light weight and easy to handle and maintain the source code if the application follows MVVM. Also People may handle different way maintain MVVM Standard in their project but the main thing is should we maintain atleast a Model a View and ofcourse a ViewModel where there no violation of the pattern. Regards Selva Ganapathy K