In WPF / XAML, should each container control contain a layout control?

Question

When designing the user interface of a WPF application in XAML, should each container control contain a layout control to host all the child controls?

Take, for example, a group unit. I can either direct the controls directly to the group box, or I can use the layout control and place the layout control inside the group field, and then manage it.

I see an advantage in the latter, because the layout control is a set of well-defined rules for children's behavior. However, at the same time, my XAML tree begins to penetrate deep into the nest and is a little more difficult to navigate.

Given this, is it always better to use layout controls or are there cases where it is perfectly acceptable to drop the control inside group boxes and tabs without one? What would be the negative consequences of this, if any?

Answer 1

There are no negative consequences when using layout panels, because even if you did not specify one, VisualTree has a default value. If you do not use it explicitly, your XAML may look cleaner.

ItemsControls StackPanel . , , , StackPanel ?

Answer 2

, , . , .

Grids, StackPanels .. , , Blend , , .

, " ", , , .