I’m writing a MVVM book – What would you like to see in it?
March 14th, 2010
I have started a quest that so many developers do; I am attempting to write a short book on the MVVM development pattern. When I say short, I mean short. Probably between 50 – 70 pages, most of it being code and examples. This is my first attempt at a book and I’m not quite sure what developers really want to know about MVVM. So please, feel free to let me know what you would like to see in a book about MVVM.
I read a really good review about what appears to be a decent 50 page MVVM book and the shortcomings of it. Check it out at: http://codebetter.com/blogs/wardbell/archive/2010/03/19/mvvm-josh-smith-s-way.aspx
If you take those suggestions into account you’ll likely have a really good book. But hard to fit into 50 pages….
Combobox selectedChange event was not handled by viewmodel.here i am taking about the event.Not the property. I think you undestood my point of view.Please explain it clearly how to handle the Selection changed event in the view-model…
I would like worked ( and explained ) examples covering real world LOB issues fully. So I would expect Database access, a datagrid and CRUD for complex ( at least parent-child ) data. Error handling. Dialogue boxes, printing and some asynchronous process handling. A book is an opportunity to start with the basics and explain them then cover both how you do the routine and handle the exceptions. On the web there are examples but they are mainly trivial. Those few that are more complex are badly explained. If you’re a genius who has worked in MVVM for years I suspect it’s difficult to work out what bits the rest of us need explaining.
It could be nice if you book has some of best practices for MVVM.
I think it would be helpful if you discuss how seperation of views from models would help different teams.
For example: When UX team designs views in the expression blend, they don’t need to interact with real models.
How to use seperate models in design mode,debug mode and release mode would be helpful.
I think giving Silverlight or WPF samples would add lot of benefit.
It would be helpful if you discuss how seperation of views from models would help different teams.
For example: When UX team designs views in the expression blend, they don’t need to interact with real models.
How to use seperate models in design mode,debug mode and release mode would be helpful.
I think giving Silverlight or WPF samples would add lot of benefit.
TDD in relation to the view model (or if it’s not do-able, then why).
I’d like to see how keyboard events (and those with key modifiers) are handled as well as drag and drop events.
I am dealing with Master-Detail scenario and MVVM for 2 months now.
Having a View with partials/regions each datatemplated with a ViewModel holding a business model , CRUD operations are not possible because the regions need data from each other like SelectedCustomerViewModel,SelectedOrderViewModel etc… but there is only DataContext for all those viewmodels (main and the regions) and I do not think we should use the Mediator pattern to shoot around the needed data between those related regions aka viewmodels.
So if you can show complex master-detail count in as your most grateful customer