Let&#39;s have a button `Command` property bound to a custom command.

When should I implement `ICommand` and when derive from `RoutedCommand`? I see that **RoutedCommand implements ICommand**.

In which case could I need to implement an `ICommand`? 
What about MVVM model? Which one suits better for this purpose?

ICommand vs RoutedCommand

I have this code (which works just right):

    &lt;KeyBinding Key=&quot;Enter&quot; Command=&quot;{Binding ReturnResultCommand}&quot;&gt;
        &lt;KeyBinding.CommandParameter&gt;
            &lt;s:Boolean&gt;
                True
            &lt;/s:Boolean&gt;
        &lt;/KeyBinding.CommandParameter&gt;
    &lt;/KeyBinding&gt;

Where &quot;s&quot; is of course the System namespace.

But this command is called quite a few times and it really inflates otherwise rather simple XAML code. Is this really the shortest notation of boolean command parameter in XAML (other than splitting the command into several commands)?

All Routed Commands Solutions on Gang of Coders

Total of 2 Routed Commands Solutions

ICommand vs RoutedCommand

Boolean CommandParameter in XAML