Hi Jenny

Suddenly now using 3.2 I'm getting a LicenseException in Blend and VS. I never had a problem with 3.1.

I'm using Composite WPF so even though I have the LicenseKey in my shell and the application runs perfectly, I can't design any views in my modules any more.

Kr

George

We still have not received your sample and the steps to reproduce the License exception.  Please note that we do not reproduce the problem in our internal tests on Blend 3 using a valid 3.2 license key of the Xceed Datagrid for WPF.  Please send us such artefact in order to get to the bottom of the Issue.

Best Regards.

Hi

Are you testing with a Composite WPF application? I have no problem with the Datagrid in any normal WPF application, it works as expected.

With the Composite application, the shell has the LicenseKey defined and the application runs perfectly.

The modules however have no knowledge of the shell and therefore will not know the LicenseKey at design time. So in Blend I get A LicenseException.

Having

Kr George

The License Exception is not reproducible in a Composite WPF application either.  Find attached a Composite WPF application project that is using an Xceed DataGridcontrol in a Module. Since the DataGridcontrol is used in a module, the licensing and the references must be set in that module.

Hi Mohamed

Your sample project gives me the License Exception as well.

Hopefully with the expected SL3 release on Friday 10th July we may get Blend 3 release too. I'll wait till Friday and see what happens.

Kr George