Home/ Questions/Q 115205
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T02:58:57+00:00

I’m trying to implement a WPF application using MVVM (Model-View-ViewModel) pattern and I’d like

  • 0

I’m trying to implement a WPF application using MVVM (Model-View-ViewModel) pattern and I’d like to have the View part in a separate assembly (an EXE) from the Model and ViewModel parts (a DLL).

The twist here is to keep the Model/ViewModel assembly clear of any WPF dependency. The reason for this is I’d like to reuse it from executables with different (non-WPF) UI techs, for example WinForms or GTK# under Mono.

By default, this can’t be done, because ViewModel exposes one or more ICommands. But the ICommand type is defined in the System.Windows.Input namespace, which belongs to the WPF!

So, is there a way to satisfy the WPF binding mechanism without using ICommand?

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. You should be able to define a single WPF custom routed command in your wpf layer and a single command handler class. All your WPF classes can bind to this one command with appropriate parameters.

    The handler class can then translate the command to your own custom command interface that you define yourself in your ViewModel layer and is independent of WPF.

    The simplest example would be a wrapper to a void delegate with an Execute method.

    All you different GUI layers simply need to translate from their native command types to your custom command types in one location.

    • 0