RelayCommand - V4 vs V3

Mar 29, 2012 at 6:36 PM

My question extends that expressed in a question on Stack Overflow - RelayCommand V4 - Can Execute Doesn't Fire.

I am a WPF developer and was wondering how this should work for me (Or a Silverlight developer I guess). We now need to:

RaiseCanExecuteChanged

On any property change which affects the command in question. What was the motivation for removing the automatic revaluation of the property?

I'm not criticising the change, just interested as to the thought process.

Thanks so much for your framework!

Gav

Coordinator
May 22, 2012 at 8:18 AM

Hey,

Sorry for the delay. In V4 RC, I restored the functionality as it was before. I really dislike the CommandManager a LOT because you basically have no control over it. I much prefer to RaiseCanExecuteChanged manually. However changing it brought more issues than it solved, notably because it is a breaking change. I thus decided to revert back to the old implementation.

Sorry for the confusion.

Cheers,

Laurent