November 5th, 2012, 01:33 PM
Single or Many ViewModels (WPF/MVVM)?
I currently have a single ViewModel decomposed internally into regions based on areas: ConnectingToFocuserMethods, ConnectingToCameraMethods, etc.
What advantages/disadvantages are there to breaking this apart into multiple view models? I currently have controls which would have a one-to-one mapping to the new view models if I break apart. Would breaking apart be a problem if I find a case where I need to bind to multiple view models from a single control/window/etc.?
Thanks for looking and any help!
Click Here to Expand Forum to Full Width
This is a Codeguru.com survey!