tags:

views:

69

answers:

1

Hi,

I'm using WPF-Prism and I'm struggling with a DelegateCommand that is not activating a button that is situated in a different region (defined in Prism). Example:

HomeTab module: I have a HomeTab module with a region for adding buttons (using Fluent ribbon) relative to the active application. Application module: I create a button view and view model and add the button to the region exposed in the HomeTab module. The button's has a DelegateCommand declared in the application module. However the button in the HomeTab region is never activating when it should be.

I tested that CanExecute was working correctly by also binding a button in the current module to the same command and it worked fine.

So the problem only occurs when the button is situated in a different region. Is this a limitation / known issue? Or am I doing something wrong.

Thanks in advance,

Ian

A: 

The error was unrelated and being caused by Unity. My apologies.

ianbeks