Sep 10, 2011 at 7:41 PM
Edited Sep 10, 2011 at 7:42 PM
Thanks for the response Graham...I'm not sure I explained my problem quite right (or maybe I don't fully understand your solution)..either way let's try this, what I hope is more clear question
Imagine (based on the 3 Part SimpleMvvm-Main example that comes with the toolkit) that each Category type item, has it's own detailViewModel and specific logic, collections and view it needs for adding and creating a item in that category, which then
comes back to the ProductListViewModel where it can be saved, removed, etc etc.
What would you do (keeping it based on the example)?
expand IProductListServiceAgent to encompass any calls needed for any of the details? or
Create ServiceAgents for each detail view model (if so, how does that code work..use the locator?)
For the viewModel and detail viewModels:
load the detail view model specific collections in the viewmodel and load up detailviewmodel there? or
load the detail specific collections in the detailviewmodel?
I'm very new to the most all of this (MVVM, Ria Services), so bare with me, I appreciate any help....just suddenly my prototype project got very popular and I need to think i terms of adding 10 to 20 new 'Items' with very different detail view models for
each, but centralizing back to 'ProductListView' where user choices will be made. Exciting times, but I also don't want to code myself into a corner or overlook a DataContext or concurrent user issue that may be out of my scope of thought.