Proposal: Make Setter.Value the ContentProperty for Setter

[Felix-Dev]

A reference to the following issue posted in the WPF repository: dotnet/wpf#84

For convenience, here is the original suggestion by @thomaslevesque:

Currently, when you want to set the value of a setter to a complex object (e.g. control template), you have to specify the <Setter.Value> element:

<Style TargetType="Button">
    <Setter Property="Template">
        <Setter.Value>
            <ControlTemplate TargetType="Button">
                ...
            </ControlTemplate>
        </Setter.Value>
    </Setter>
</Style>

But this element brings no value at all, it just adds noise. Making Value the ContentProperty for Setter would make the code a bit less verbose:

<Style TargetType="Button">
    <Setter Property="Template">
        <ControlTemplate TargetType="Button">
            ...
        </ControlTemplate>
    </Setter>
</Style>

Certainly, in my opinion, one of those small changes which will make XAML programming more convenient.

[jevansaks]

Great feedback! I've filed an internal issue on the parser team for tracking.

[michael-hawker]

Is there more required here beyond just setting the ContentProperty attribute built-in to the framework?

[evelynwu-msft]

Is there more required here beyond just setting the ContentProperty attribute built-in to the framework?

Probably not; I don't recall Setter.Value being a property that we do tricky things with under the cover.