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
|
It seems that with WPF Elements 5.1.1283.20767 there is a dependency of the DataGrid on Mindscape.WpfElements.Spin.lic. I have all external assemblies placed in a folder at the Visual Studio solution directory level. That way all developers/build server can build using a relative path for all external references. Thus, when I get an update from Mindscape, I copy the Mindscape.WpfElements.dll and the necessary .lic files into my external assemblies folder. With this particular version (5.1.1283.20767) I would get an exception when compiling my project ("No license installed"). I changed my reference to use the Mindscape.WpfElements.dll from the installation path, and my project would build without the license exception. So, I copied all the .lic files from the installation path to my external assemblies path and referenced the Mindscape.WpfElements.dll from the external assemblies path. The project built without a problem. So, through the process of elimination, I determined that the Mindscape.WpfElements.Spin.lic file must also exist in the external assemblies folder. The only control that I'm using from WPF Elements currently is the DataGrid control. I have the following files in the external assemblies folder: Mindscape.WpfElements.dll Mindscape.WpfElements.DataGrid.lic Mindscape.WpfElements.Spin.lic Why is the Mindscape.WpfElements.Spin.lic needed for the DataGrid? I suppose that this might be a mistake. Thanks. |
|
|
|
|
Hello Jared The DataGrid does in fact use the Spin control. There is a hidden one in the built in pager. Even when it is not displayed it's best to have the .lic file. I'm not sure why you've only just run into this problem now though. In general it's best to just include all .lic files along side the dll. This is to avoid situations where a new feature or improvement suddenly causes a control to use another control in the style. I hope there isn't any problem with including all the .lic files or at least just the Spin license in your external assemblies folder. Note that we do have plans to make the licensing more convenient in the next major version. Jason Fauchelle |
|
|
|
|
I can include the .lic files with the .dll file. It is more of an inconvenience than a major problem. I anticipate having many projects that depend on WPF Elements, but I was hoping to limit the number of copies of files that I'm copying to the external asseblies folder for each solution/project. Thanks for the information. I'd love to see the licensing improved in the future. |
|
|
|
