-
November 5th, 2012, 02:33 PM
#1
Single or Many ViewModels (WPF/MVVM)?
Hi,
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!
Alan
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|