Hi Ross,

Have you managed to get the UXMaskedInput work in your end?

Thanks,
Jimmy

The quality of the sample code definitely does not reflect the quality of the controls engineering. A large portion of the samples were built only to demonstrate the user interface and control-related features, while you will find a subset of samples that were pretty good, such as the contacts and other MVVM example to demonstrate MVVM best practice.

Unlike other vendors, we don't provide source code. We can't even if we want to, because a number of our user interface technologies are patented (or patent-pending). Intersoft has been all about quality and innovation, thus we have a very different business model with the other vendors. I trust our customers have seen our differences, and what really sets us apart.

For investment protection and security, we provided annual ESCROW subscription through a well-known third party vendor based in Canada. For further information, please contact our sales team.

Hope this helps,
Jimmy

Hi Andre,

Yes, you can use SL toolkit side-by-side with ClientUI.

You may want to ensure that the toolkit assembly that contains the "NumericUpDown" is properly referenced in your project.

Hope this helps.

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.

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