It seems currently there is some issue with commanding in WPF ClientUI. I have forwarded this issue to the developer for further investigation, I will inform you of any update.

Harry,

The CommandBinding object is inadvertantly missing in the ClientUI Framework for WPF library. This has been addressed in the upcoming December build with feedback reference #868.

When using the shared model in the code (C#), make sure you mapped the assembly reference correctly as pointed in Unified Development Model (ClientUI documentation), under the "Class Library & API" section.

Hope this helps,
Jimmy

So again to be clear - I can't make the WPF routed command version work until I download a new build of the ClientUI framework?

Also how do I find out about the update i.e what do I do with  "feedback reference #868".

Also I'm evaluating the software using the trial version - will the update work with this?

You can make the WPF version of routed command work using code behind at the meantime. You still can use the same command, the difference is just at the registration/declaration process. Later when the XAML object is available, you can easily delete the workaround code and use the XAML declaration instead.

When an update is released, we published the changes log which contains the feedback reference (or also called work item). This allows customers to match their submitted issues with the version history.

The update won't work for trial version, but you can re-download the new setup that contains the new assemblies, or we can send you the latest assemblies privately.

Ok, thanks and I follow the answer perfectly.

I will look out for the update and redownload the trial - I assume that this doesn't trigger any problems with the licence (time remaining etc.)

Any progress on the update?

Using the latest ClientUI, ClientUI 4, commanding has run without any issue in WPF.