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
|
I am also experiencing a licensing issue here, which will not go away even though I have been working in it for the past 3 hours. License.licx displays: Mindscape.WpfPropertyGrid.PropertyGrid, Mindscape.WpfPropertyGrid, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0f2f2e3bf9b0527c Mindscape.WpfPropertyGrid.dll referenced within my project is compiled from source and not the version installed with the product in c:\program files.... Mindscape.WpfPropertyGrid.PropertyGrid.unrestricted.lic was also copied from source location \Bin to a central Libraries\Debug folder where the compiled dll resides. Lic file has also been added to the project that will be using the property grid. This project is a DLL output type and not an EXE. Despite all of this, I get both compile and run time errors: Compile time error says; Error 2 Could not create an instance of type 'PropertyGrid'. C:\dev\LUT600 2.1.1\OCC600\Source\Libraries\ControlsLibrary\wpf\Routing\RouteLinkEditor.xaml 14 9 ControlsLibrary
Runtime error says: Error 1 Exception occurred creating type 'Mindscape.WpfPropertyGrid.PropertyGrid, Mindscape.WpfPropertyGrid, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0f2f2e3bf9b0527c' System.ComponentModel.LicenseException: An instance of type 'Mindscape.WpfPropertyGrid.PropertyGrid' was being created, and a valid license could not be granted for the type 'Mindscape.WpfPropertyGrid.PropertyGrid'. Please, contact the manufacturer of the component for more information. C:\dev\LUT600 2.1.1\OCC600\Source\Libraries\ControlsLibrary\Properties\licenses.licx 1 ControlsLibrary
This has been a frustrating experience upon first use. I hope it gets better after this is resolved :).
|
|
|
Hello Klaus, Sorry you're having a frustrating experience with this. I hope we can resolve it quickly for you. Let me just make sure I have understood what you have done: * You have compiled the control from the source code and copied the compiled DLL to a Libraries/Debug folder, and you are referencing the DLL at that location. * You have also the .unrestricted.lic file from the source code build output location to Libraries/Debug. If this is correct, what you need to do is either: * Copy Mindscape.WpfPropertyGrid.PropertyGrid.lic (without the .unrestricted qualifier) to Libraries/Debug. You can find this in the source code build output location, or the installation folder, or the WpfPropertyGrid project folder; or * Rename the .unrestricted.lic file in the Libraries/Debug folder to Mindscape.WpfPropertyGrid.PropertyGrid.lic. The background to this is that the .xyz.lic files are actually used by the script that builds our installers (which renames them before building). They are not intended for direct customer use as licence files. A future release will make this clearer by renaming these files to .lictemplate to indicate that they are *used to create* licence files rather than being licence files themselves. We had not anticipated that customers would use these files, but in retrospect I can see that copying them to the output location was potentially confusing. We apologise for the confusion and once again I'm sorry you've had a frustrating experience with this. |
|
|
Wow, that was relatively painless. I am no longer getting any compile time errors, thank you. However, you did not mention that the .lic file should also be copied to the application's output directory for runtime validation! In effect, the .lic file must be copied to two different locations to cater for compile and runtime scenarios. This is indeed cumbersome, unless I am missing something here. This is the first third party control that I have had to deal with such licensing issues. Why do you not consider embedding licensing into the control using a property like other vendors do? Now, is there anything that is preventing your assembly from being copied to my application's output directory even though its 'Copy Local" property is set to true? |
|