I got the following code from Josh Smith\'s MVVM tutorial.
Can anyone provide a quick explanation of what this code actually does?
public event Event
CanExecuteChanged
notifies any command sources (like a Button
or MenuItem
) that are bound to that ICommand
that the value returned by CanExecute
has changed. Command sources care about this because they generally need to update their status accordingly (eg. a Button
will disable itself if CanExecute()
returns false
).CommandManager.RequerySuggested
event is raised whenever the CommandManager
thinks that something has changed that will affect the ability of commands to execute. This might be a change of focus, for example. Turns out that this event fires a lot.So, in essence, what this bit of code does is ensure that whenever the command manager thinks a command's ability to execute has changed, the command will raise CanExecuteChanged
even if it hasn't actually changed.
I actually dislike this approach to implementing ICommand.CanExecuteChanged
- it feels lazy and isn't entirely reliable. I prefer a much more fine-grained approach where the command exposes a method (eg. RaiseCanExecuteChanged()
) you can call to raise CanExecuteChanged
, then you call this at the appropriate times from your view model.
For example, if you have a command that deletes the currently selected customer, it would have a CanExecute()
handler that returns true
only if there is a customer selected. You would therefore call RaiseCanExecuteChanged
whenever the selected customer changes.
RoutedCommands
can automatically notify if their CanExecute
has changed, since we are implementing ICommand
here, which the WPF system doesn't know about, we wire them to CommandManager's RequerySuggested
event. CanExecuteChanged
is raised. As your button is listening to this event it will reinvoke CanExecute
to know the latest status.Here is an article that might be of interest.