ICommand Interface
Defines a command.
Namespace: System.Windows.Input
Assemblies: System (in System.dll)
System.ObjectModel (in System.ObjectModel.dll)
XMLNS for XAML: Not mapped to an xmlns.
[TypeConverterAttribute("System.Windows.Input.CommandConverter, PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, Custom=null")] public interface ICommand
<object property="predefinedCommandName"/>- or -<object property="predefinedCommandName.predefinedCommandName"/>- or -<object property="{x:Static customClassName.customCommandName}"/>
XAML Values
The ICommand type exposes the following members.
| Name | Description | |
|---|---|---|
  | CanExecute | Defines the method that determines whether the command can execute in its current state. |
| Execute | Defines the method to be called when the command is invoked. |
| Name | Description | |
|---|---|---|
| CanExecuteChanged | Occurs when changes occur that affect whether or not the command should execute. |
RoutedCommand and RoutedUICommand are two implementations of the ICommand interface in Windows Presentation Foundation (WPF).
ICommand in Windows Runtime apps
The ICommand interface is the code contract for commands that are written in .NET for Windows Runtime apps. These commands provide the commanding behavior for UI elements such as a Windows Runtime XAML Button and in particular an AppBarButton. If you're defining commands for Windows Runtime apps you use basically the same techniques you'd use for defining commands for a .NET app. Implement the command by defining a class that implements ICommand and specifically implement the Execute method.
XAML for Windows Runtime does not support x:Static, so don't attempt to use the x:Static markup extension if the command is used from Windows Runtime XAML. Also, the Windows Runtime does not have any predefined command libraries, so the XAML syntax shown here doesn't really apply for the case where you're implementing the interface and defining the command for Windows Runtime usage.
