Gets or sets the ICommand associated with this input binding.
Assembly: PresentationCore (in PresentationCore.dll)
XMLNS for XAML: http://schemas.microsoft.com/winfx/2006/xaml/presentation, http://schemas.microsoft.com/netfx/2007/xaml/presentation
'Declaration <LocalizabilityAttribute(LocalizationCategory.NeverLocalize)> _ <TypeConverterAttribute("System.Windows.Input.CommandConverter, PresentationFramework, Version=188.8.131.52, Culture=neutral, PublicKeyToken=31bf3856ad364e35, Custom=null")> _ Public Property Command As ICommand
<inputBindingDerivedClass> <inputBindingDerivedClass.Command> <iCommandImplementation/> </inputBindingDerivedClass.Command> </inputBindingDerivedClass>
Property ValueType: System.Windows.Input.ICommand
The associated command.
The InputBinding class does not support XAML usage because it does not expose a public default constructor (it has a default constructor, but it is protected). However, derived classes can expose a public constructor and therefore, can use properties that are inherited from InputBinding. Two existing InputBinding derived classes that can be instantiated in XAML and can set properties with XAML usages are KeyBinding and MouseBinding.
ICommand references a type converter that enables certain preexisting ICommand implementations to specify values in the form of a string. This type conversion behavior sets the attribute value form of this property. You can also bind the , CommandParameter, and CommandTarget properties to an ICommand that is defined on an object. This enables you to define a custom command and associate it with user input. For more information, see the second example in InputBinding.
Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.