MVVM approach, what's a good way? How to improve/speed up development? <p>this post is meant to have a list of suggestions on MVVM approach... What tools do you use, what do you do to speed up development, how do you maintain your application, any special ways of finding defects in this design pattern......</p> <p>here is what I do:</p> <p>So first i create my model/db with EF.</p> <p>Then I create Views (either user controls or windows) with their respective viewmodel. I usually place the viewmodel in the same location as my view. But while starting the name of my view with "UC-name", I call my viewmodel just "name-model".</p> <p>In my viewmodel I implement InotifyPropertyChanged</p> <p>in my xaml view I have a resource of my viewmodel, and bind my grids/controls via the itemsource to the staticresource.</p> <p>I try to do a lot of front end logic with triggers and styles and also place some code in the xaml.cs file if it regards logic for behaviour of my controls.</p> <p>I can reach my viewmodel from my view (xaml + xaml.cs).</p> <p>for communiation between viewmodels I use MVVM lights.</p> <p>that's pretty much it.</p> <hr> <p>Things I'm thinking about</p> <ul> <li><p>I'm thinking of using T4 templates for generating viewmodel/view. What do you guys think of this. is this worth it?</p></li> <li><p>when using MVVM light Messenger, we get a subscription based communication, and sometimes I find it hard to track what has changed in my DataContext. Any suggestions on this?</p></li> <li><p>any other improvements or suggestions are more than welcome !</p></li> </ul>