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
|
Today I moved some code from one solution to another. I found I had to delete and re-add Mindscape.WpfDiagramming assembly references to resolve compile-time "No license installed" exceptions. Now upon running my application, I get a licensing exception when the Window containing my diagram is opened. Properties/licenses.licx is an Embedded Resource in the project. The Window containing my diagram is in a class library referenced by my application. Do I need to include a licenses.licx in the executable as well as the assembly where the diagram lives? If so, is there a way around this limitation? I need to deploy my class library as a standalone DLL. |
|
|
|
|
I confirmed that adding Mindscape assembly references and the licx file to the executable (not just the class library where the window resides) works around the problem. Kindly let me know how I can deploy my class library without requiring consumers to jump through such hoops. |
|
|
|
|
Hello ed The standard .NET licensing system requires the host to have the licenses file. When you have an application that references your class library, which in turn references WPF Diagrams, both the class library and the application need the licenses file to run. When you ship your application, visual studio will compile the licenses file into the binaries, so your customers won't need the licenses file. If this does not answer you questions, please let us know more about your application. If you can send us a sample project of what you are working on, this will help us to understand the problem. Jason Fauchelle |
|
|
|
