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
|
Hello, We have purchased four licenses for our company and we are running into issues when we check out another developers code from source control. All developers have valid Mindscape license loaded on their machines. The checked out project shows license errors on Mindscape controls, but if I close that project down and create a new sample project that contains Mindscape controls everything works fine. Only the original developer is able to use the code with no errors. What is the solution to this license issue? |
|
|
Hello Take a look at this licensing faq which covers the common causes of licensing exceptions: http://www.mindscapehq.com/forums/thread/1309 If any of the machines had a trial version installed, this should be uninstalled first. Also make sure all the developers machines have the full version of WPF Elements installed on each them. If you haven't done so already, the Properties folder of the project needs a .licx file. This should be copied from one of the samples that ships with WPF Elements. Jason Fauchelle |
|
|
Thanks, I had to remove my references and then add them again to get the solution to build. Ed |
|
|
Same here. Each time I move to another machine, I need to remove and re-add my references to Mindscape assemblies to make Visual Studio happy. Is there a way to automate this process? |
|