1

Can I have multiple ViewModel for a View in WPF? Because some times we need to show the view only in simple view format and sometimes the same view has to shown in editable format. Hence we can create seperate view models for each.

So is there any way to hook 2 diffrent view models to a view?

WPFProgrammer
  • 251
  • 2
  • 8

2 Answers2

2

A ViewModel should serve as the Data Context for your View, so that would only allow a single VM.

There is no reason why you could not break you View up in to multiple UserControls, each with their own ViewModel.

benPearce
  • 37,735
  • 14
  • 62
  • 96
  • Is there a source for where this rule is defined? I'm keen to know what best practice this is braking. – Chucky Jun 05 '18 at 08:51
  • @Chucky what rule are you referring to? The view DataContext can only be assigned a single object. That could be a view model which comprises other view models as well. – benPearce Jun 06 '18 at 12:10
  • I understand. I think I misunderstood. One ViewModel for one DataContext. – Chucky Jun 06 '18 at 12:40
1

Generally you're going to bind your View to a single type of View Model. That's not to say that your type couldn't be an interface, or a base class from which both of your views inherit.

I tend to only use an interface or base/derived class situation when I have a single view model type that is going to span several different views. For example if I have two different types of forms that display widget information, I would create a single base Widget ViewModel class.

In your case, it sounds you should either a.) create two views for your simple and advanced views or b.) simply use a single ViewModel class.

Justin Beckwith
  • 7,686
  • 1
  • 33
  • 55