0

I’m taking a lot of worry selecting an MVVM framework to convert to. One of the major considerations is support for User Controls and nested user controls as my main page today has a user control that contains nested user controls.

The author of Catel highlights lack of support for nested user contorls as a major disadvantage of other platforms (inc. Caliburn.Micro)

So my question is: Doesn't Caliburn.Micro support nested user controls?

Dave Clemmer
  • 3,741
  • 12
  • 49
  • 72
Avi
  • 15,696
  • 9
  • 39
  • 54

1 Answers1

1

Caliburn.Micro doesn't place any restrictions on the types of mechanisms you use for developing your user interface. It isn't a requirement to use Caliburn.Micro's conventions, you can still be explicit with your bindings when required.

If you are using user controls to reuse user interface code during view composition, then Caliburn.Micro provides an alternative technique for this too, using view model properties and ContentControls.

See here for an example.

Community
  • 1
  • 1
devdigital
  • 34,151
  • 9
  • 98
  • 120
  • That's a great question you linked to ;). However, how does it work with nested user controls? – Avi May 30 '12 at 13:10
  • Are you using nested user controls purely for view composition? If so, you would use the same technique as shown in that question on your child view models. i.e. they would also have public properties that are other view model instances, and you would use ContentControl's on their respective views to reuse views and presentation logic. – devdigital May 30 '12 at 13:22