Is there some way to avoid implement ICommand to can use a Button in MVVM?

relaycommand example wpf mvvm
relaycommand canexecute
mvvm light relaycommand
mvvm icommand
mvvmlight eventtocommand
wpf relaycommand with parameter
mvvm button click

I am developing a very simple application, a view with few buttons. I would like to can use the click event of the buttons in the view model.

But the I have only found examples that need to use the Interactivity.dll from blend, or I have to implement the ICommand interface or some other solutions.

I would like to know if there are any solution now days that doesn't need to implement ICommand or use frameworks like MVVM Light. I would like to use the most simple solution.


Why are you so averse to using ICommand? If you're going to follow the MVVM pattern, it's the perfect way to achieve separation between the UI and business logic layers.

The most basic implementation of ICommand is just something like this

/// <summary>
/// a very simple ICommand implementation
/// </summary>
public class BasicCommand: ICommand
    private readonly Action _execute;

    public BasicCommand(Action execute)
        _execute = execute;

    public bool CanExecute(object parameter)
        return true;

    public void Execute(object parameter)

    public event EventHandler CanExecuteChanged;

More advanced implementations of ICommand such as the MVVM-Light RelayCommand one also take care of disabling any bound control (e.g. button or menu item) as required through the CanExecute mechanism, in a much more decoupled and cleaner way than trying to set Button.InEnabled.

c#, Is there some way to avoid implement ICommand to can use a Button in The most simple solution is to use a framework like MVVMlight or  In this article, we will learn about button click event in WPF with MVVM concept. We use ICommand interface for generating the button click event. Let's take one simple example of one simple textbox and button. After writing the text in textbox, when we click on button, it will display a simple message box.

Why do you want to avoid ICommand?

You can write your own implementation of ICommand but this is unnecessary when MVVM Light has all of the tools and is easy to use.

If your app is that simple, your choices are:

  1. Ignore MVVM pattern and just implement event handlers in code behind

  2. (I suggest) Use MVVM Light with the default ICommand implementation

    public RelayCommand ExampleRelayCommand => new RelayCommand(ExampleMethod);

    private void ExampleMethod()
  3. If you want the EventArgs then you can implement interactivity triggers and EventToCommand using PassEventArgsToCommand="True" also using MVVM Light

        public RelayCommand<RoutedEventArgs> EventRelayCommand => new RelayCommand<RoutedEventArgs>(EventRelayCommandMethod);
    private void EventRelayCommandMethod(RoutedEventArgs e)

Then, inside the button in XAML:

<Button Grid.Column="0" Content="Example"> <i:Interaction.Triggers> <i:EventTrigger EventName="Click"> <command:EventToCommand Command="{Binding EventRelayCommand}" PassEventArgsToCommand="True" /> </i:EventTrigger> </i:Interaction.Triggers> </Button>

Is there some way to avoid implement ICommand to can use , Is there some way to avoid implement ICommand to can use a Button in MVVM? I would like to can use the click event of the buttons in the view model. But the  You can't bind directly to a method because Button (for example) doesn't have a property that accepts a delegate. Instead, it has a Command property of type ICommand. A RelayCommand (aka DelegateCommand) is just an ICommand that wraps delegates.

You may want to take a look at Caliburn.Micro. It's a MVVM library that lets you define methods without any commands in your view model and bind to them using naming conventions:

View Model:

public void Click() { /* handle */ }


<Button Content="Click!" x:Name="Click" />

Another option would be to add a click event handler to your view's code-behind class and call a mehod of the view model from there:

private void Button_Click(object sender, RoutedEventArgs e) 
    => (DataContext as GeneralOptionsViewModel).Click();

Then you don't use any commands but you still keep the application logic in the view model.

Windows 8.1 Apps with XAML and C# Unleashed, Following an MVVM architecture means avoiding—sometimes completely It's any object implementing the ICommand interface from the System. This doesn't sound much better than simply using events, however, unless you're and MenuFlyoutItem have a Command property that can be set to any ICommand (​plus a  This video explains how to use ICommand Interface while working with MVVM Pattern in WPF. As prerequisite its better to have knowledge of WPF and MVVM pattern. If you are new to MVVM Pattern

Real World .NET, C#, and Silverlight: Indispensible Experiences , Applying the MVVM Pattern Because you must keep the code-behind as clean as possible, you can't start adding event handlers to it. Instead, you can use commands. Using a command, you can link an action in the ViewModel to an event in the To use a command, you must write a class that implements the ICommand  The ICommand interface is generally used in the MVVM architecture. Here in the Button control the Command property is bound to the "UpdateCommand". Since UpdateCommand is nothing but an ICommand instance, while loading the window it will check the CanExecute return value and if it returns true then it will enable the button control and the

Windows Presentation Foundation Development Cookbook: 100 recipes , If you now navigate to the MainWindow.xaml.cs file, you won't see any In the MVVM pattern, our intention is to keep the code-behind file Note that the MVVM is not a framework, but in using this pattern you can create a framework. The class RoutedCommand implements the ICommand interface and allows the  My approach to avoid UI freezing in these scenarios is to use async/await in the ICommand execution, and execute the long-running code on a background thread. Your modified code would look something like this:

Pro XAML with C#: Application Development Strategies (covers WPF, , As you can see, the C# code is imperative, which means that the application is in lines of code where each line illustrates how the control instances are created. for the technologies you will be using to build a solid, robust, loosely coupled, to bind the Command property of a Button to an ICommand implementation in  CanExecuteChanged is invoked when changes occur that can change whether or not the command can be executed. CanExecute will determine whether the command can be executed or not. If it returns false the button will be disabled on the interface. Execute runs the command logic. With a simple implementation of ICommand I can create the following:

  • The most simple solution is to use a framework like MVVMlight or ReactiveUI or ...
  • One of the reasons it is to know if there are another alternatives, and also because I have to implement the same ICommand in all the projects, so I wanted to know that if it would be a more direct way to bind the command.
  • There are always alternatives, but none are as clean or elegant as using ICommand.