I’m not sure why it never occurred to me before, but this might help clean up some of the code out there where buttons are bound to commands.

The standard way I have been binding to buttons is to set the command and then set the content like one of the following:

<Button x:Name="PlayButton" 
        Command="{Binding PlayCommand}">Play</Button>
<Button x:Name="Help"
        Content="{Binding RelativeSource={RelativeSource Self}, 
                 Path=Command.Text}" />

Which in the first case just repeats the word “Play” three times and in the second case is just plain ugly and not something you would want to reproduce everywhere just to infer the content from the Command when typing “Help” would be easier to type and to read. Yeah obvious, now that I spell it out to myself. I should just set my default style on my buttons to be something like this and include it in my skins/app.xaml

<Style TargetType="Button">
  <Setter Property="Content" 
          Value="{Binding RelativeSource={RelativeSource Self}, 

Now all buttons will try to set their content to the Command’s Text property if it has one (RoutedUICommands do). If the command doesn’t expose a Text Property or the button is not bound to a command, well I still was going to have to code some content anyway so no big loss.