Understanding Commands in WPF: A Cleaner Alternative to Button Click Events

Many WPF developers start by using Button Click events for handling user actions. At first, this seems simple and straightforward. But very soon, the code-behind file becomes huge, and maintaining it turns into a challenge.

One big problem arises: when the logic changes, the button does not enable or disable automatically, and testing button click logic becomes very difficult.

So the big question is:
Is there a better way to handle button actions in WPF?

The answer is Commands.

In this post, we’ll learn how to use Commands in WPF with a simple, practical example. We’ll cover:

• What a Command is

• How it works

• Why using Commands is better than Click events

• How buttons can automatically enable or disable based on conditions

---

What is a Command in WPF?

In WPF, a Command acts as a middle layer between the UI and your logic. Instead of the button directly calling a method, it triggers a Command, and the Command decides:

• What code should run

• Whether the button should be enabled or disabled

This keeps the UI clean and ensures that all logic is centralized. Commands also make your code easier to unit test, which is essential in professional applications.

---

Writing a RelayCommand

Here’s a simple implementation of a RelayCommand:

using System;

using System.Windows.Input;

public class RelayCommand : ICommand

{

    private readonly Action _execute;

    private readonly Func<bool> _canExecute;

    public RelayCommand(Action execute, Func<bool> canExecute = null)

    {

        _execute = execute;

        _canExecute = canExecute;

    }

    public bool CanExecute(object parameter)

    {

        return _canExecute == null || _canExecute();

    }

    public void Execute(object parameter)

    {

        _execute();

    }

    public event EventHandler CanExecuteChanged;

    public void RaiseCanExecuteChanged()

    {

        CanExecuteChanged?.Invoke(this, EventArgs.Empty);

    }

}

Using Commands in Your ViewModel or Code-Behind

Let’s say you have a Register button that should only be enabled when the user fills in all fields. Here’s how you can wire it up:

public ICommand RegisterCommand { get; }

public MainWindow()
{
    InitializeComponent();
    this.DataContext = viewModelObject;
    RegisterCommand = new RelayCommand(Register, CanRegister);
}

private void RaiseCanExecuteChanged(object? sender, PropertyChangedEventArgs e)
{
    RegisterCommand.RaiseCanExecuteChanged();
}

private bool CanRegister()
{
    return !string.IsNullOrWhiteSpace(FullName)
        && !string.IsNullOrWhiteSpace(Email)
        && !string.IsNullOrWhiteSpace(Password);
}

Any property on which the button’s enabled state depends should notify the command when it changes:

private bool _canSave;

public bool CanSave

{

    get => _canSave;

    set

    {

        _canSave = value;

        // IMPORTANT: notify command that condition has changed

        SaveCommand.RaiseCanExecuteChanged();

    }

}

Why Commands Are Important in Real Projects

Using Commands in WPF brings many benefits:

• Automatic UI updates: Buttons enable or disable automatically when conditions change

• No manual IsEnabled handling in XAML

• Easy unit testing: Test your logic without opening the UI

• Reusability: Same command can be used in multiple places

• Clean separation of UI and logic: Keeps your application maintainable

This is why professional WPF applications avoid using Button Click events for handling logic.

Key Takeaways

By the end of this post, you should understand:

• What a Command in WPF is?

• How a button executes logic using a Command?

• How a button enables or disables automatically?

• Why this approach is great for clean code and unit testing?

If you want your WPF applications to be maintainable, testable, and professional, learning and using Commands is essential.