This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
After installing the most recent nightly build, I'm getting the following error when I try to run: LicenseException occurred: An instance of type 'Varigence.Windows.Controls.DataflowDiagramSurface' was being created, and a valid license could not be granted for the type 'Mindscape.WpfDiagramming.Foundation.DiagramSurface'. Please, contact the manufacturer of the component for more information. |
|
|
More information: I tried the following: 1) Uninstall diagramming 2) Reboot 3) Install the original 1.0 bits 4) Try to open the sample solution. I get the same error. Is there something in the registry or elsewhere that I can clear out to make this work? We're basically blocked on this right now. |
|
|
Hello Scott, The most common causes of this error are covered at http://www.mindscape.co.nz/forums/Thread.aspx?ThreadID=1309 (this talks about another control but it is equally applicable to the diagram control). Assuming no other changes in your project, my best guess is that you might have inadvertently downloaded and installed the trial edition (though the fact that you've reinstalled mitigates against this). Could you have a look in the .lic file (at the reference location if you are using a project Libraries directory): if the first four characters are ZTJ2 then it is a trial licence, if the first four characters are V3QS then it is a retail licence. |
|
|
I found potentially another item for the LicenseException FAQ - not sure how common it will be, though. Somewhere along the way, an intermediate daily build was added to the GAC. When I upgraded to the latest daily build, the load failure manifested as a licence exception. When I reverted back to v1.0, the GAC still did not match the the reference, so I had the same outcome. Removing the assemblies from the GAC fixed the problem. |
|
|
I'll get that added to the FAQ -- thanks for the info! |
|