Auto Command binding

WPF ICommand interface is the canonical way to expose commands from a ViewModel that is bound to a View. They come with a few caveats:
Most of the times commands are simple and the plumbing required to create an ICommand implementation is not worth it.
ViewModels exposing commands that implement the ICommand interface reference WPF types with the risk of complicating the required testing infrastructure.
Radical solves the above issues by introducing a handy markup extension that allow to write a ViewModel like the following:
1
class MyViewModel : AbstractViewModel
2
{
3
   public void DoSomething()
4
   {
5
      //perform work
6
   }
7
}
Copied!
The DoSomething method can be bound to a Button on the View in the following manner:
1
<Button Command="{markup:AutoCommandBinding Path=DoSomething}" />
Copied!
The AutoCommandBinding markup extension will dynamically build a DelegateCommand that wraps at runtime the method invocation.
The ICommand interface exposes a CanExecute(object) method that the WPF inteface can call to detect if the command is available in the current context and thus decide if the WPF element bound to a command should be enabled or not. Using the same approach as above a ViewModel can expose a bool property as following:
1
class MyViewModel : AbstractViewModel
2
{
3
   public void DoSomething()
4
   {
5
      //perform work
6
   }
7
   
8
   public bool CanDoSomething
9
   {
10
      get{ return true; /* or false */ }
11
   }
12
}
Copied!
The convention is to expose a public boolean property whose name is the same as the method, that will be wraped in a command, prefixed with Can. No changes to the XAML markup are required.
Given the way commands work in WPF one thing that might be required is to change the command status, and thus the bound control, from the ViewModel implementation. The easiest thing is to ask WPF to reevluate the Can* boolean property whenever we decide the command status changes. We can leverage the power of Radical properties metadata, and specifically the cascade changes notification feature as following:
1
class MyViewModel : AbstractViewModel
2
{
3
   public MyViewModel()
4
   {
5
        this.GetPropertyMetadata( () => this.SelectedEntity )
6
            .AddCascadeChangeNotifications( () => this.CanEdit );
7
   }
8
   
9
   public MyEntity SelectedEntity
10
   {
11
      get { return this.GetPropertyValue( () => this.SelectedEntity ); }
12
      set { this.SetPropertyValue( () => this.SelectedEntity, value ); }
13
   }
14
​
15
   public void Edit()
16
   {
17
      //perform work
18
   }
19
   
20
   public bool CanEdit
21
   {
22
      get{ return this.SelectedEntity != null; }
23
   }
24
}
Copied!
In the above scenario whenever the SelectedEntity property changes a INotifyPropertyChanged.PropertyChanged event is raised also for the CanEdit property, thus WPF reevaluates the property and based on the boolean result the bound command will be enabled or not.
The markup extension is defined in the http://schemas.radicalframework.com/windows/markup xml namespace.

Markup Extensions - Previous

Editor binding

Next - How to

Get the view of a given view model

Last modified 7mo ago

Copy link