Home/ Questions/Q 6985459
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T18:40:59+00:00

I have a co-worker that asked me why he has to use the ICommand

  • 0

I have a co-worker that asked me why he has to use the ICommand pattern.

He wants to add a button and then make an event for it in the code behind. Then from the event he wants to call a method on the ViewModel.

I gave him the obvious answer: This adds coupling between the View and the ViewModel. But he argued that the View and the ViewModel are already coupled. (We set our view’s DataContext to the ViewModel in the View’s code behind: DataContext = new MyViewModel();

Yes, I told him that his way adds “more coupling”, but it sounded a bit lame even to me.

So, I know that ICommand is the clean way, and I do it that way. But what else does ICommand buy you besides not using an already existing coupling?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    • It’s not about decoupling, but how deep you can penetrate inside your ModelView hierarchy: not event pumping, but event routing, built-in in the framework.

    • It’s about UI managent: Command has state (CanExecute), if assign the command to the control, if command’s state becomes false, control becomes disabled. It gives you powerful UI state management way, avoiding a lot of spaghetti coding, for complicated UI especially.

    • 0