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 having an issue with one of the WPF Elements nightly builds causing a license exception. This causes all Mindscape controls to disappear from my UI. Everything worked fine with the full verion WPF Elements version 6. |
|
|
|
|
Hello License exceptions are supposed to cause the project to fail to compile. I've never heard of a scenario where the controls disappear. I have done a fresh install of the latest nightly build from our store, but have not come across any license or control issues. Could you please provide more details about the exception and I'll look into it further. -Jason Fauchelle |
|
|
|
|
Here is the error I receive: Error 27 Exception occurred creating type 'Mindscape.WpfElements.Charting.Chart, Mindscape.WpfElements, Version=6.0.2165.22593, Culture=neutral, PublicKeyToken=0a92c4b7d9c14aa4' System.ComponentModel.LicenseException: A valid license cannot be granted for the type Mindscape.WpfElements.WpfElementsCore. Contact the manufacturer of the component for more information. Error 28 Exception occurred creating type 'Mindscape.WpfElements.ColorPicker, Mindscape.WpfElements, Version=6.0.2165.22593, Culture=neutral, PublicKeyToken=0a92c4b7d9c14aa4' System.ComponentModel.LicenseException: A valid license cannot be granted for the type Mindscape.WpfElements.WpfElementsCore. Contact the manufacturer of the component for more information. I have license entries for both of these components in my License.licx file. I also have a Mindscape.WpfElements.WpfElementsCore.lic file where I reference the Mindscape.WpfElements.dll |
|
|
|
|
Hello It sounds like your setup is correct. Does the installed SampleExplorer work if you run the source from VS? In any case, here are some things to try next: Uninstall and reinstall the latest nightly build downloaded from your account page. Clean your visual studio solution and delete the bin and obj folders if they remain. Delete you licx files (or remove the WPF Elements related bits if they contain other licenses) and then paste the entry of one of the licx files from the samples. Closely follow this FAQ: http://www.mindscapehq.com/forums/thread/1309 It refers to WPF Property Grid, but it applies the same to WPF Elements. If you don't mind, I'd like to know which solution solves the problem. Regards -Jason Fauchelle |
|
|
|
|
I wanted to mention that I also have experienced design-time licensing errors, with no problems compiling. I get this problem on and off, and I think it may be caused by my switching between including the source code as a project in my solution and just referencing the WpfElements dll. When is happens it is always Mindscape.WpfElements.WpfElementsCore for which the license cannot be granted, and the Mindscape controls do not show up in the designer. Peter |
|
|
|
|
I have been busy working on other task, but this problem still persist! I have completely uninstalled Visual Studio 2010 and WPF Elements nightly build. After re-installing Visual Studio 2010 and install WPF Elements Version 7, the problem still remains. I get this error:
I am completely unable to work with the tools now |
|
|
|
|
Hello If you are seeing this message as a compile time error, then the most likely cause of the issue is the Mindscape.WpfElements.WpfElementsCore.lic file is missing from the bin folder where you are referencing the WPF Elements dll. To solve, copy the lic file from the WPF Elements install bin folder into the folder where you reference the dll. If this message is a run time exception, then the most likely cause is that the .licx file in the properties folder of your projects(s) may be either missing, or may not include the line for WpfElementsCore 7.0.0.0. If this is the case, go to the Samples folder and copy one of the licx files from one of the samples. If the problem remains, please follow this faq: http://www.mindscapehq.com/forums/thread/1309 Please let me know which point solves the problem. -Jason Fauchelle |
|
|
|
|
I am referencing my Mindscape.WpfElements.dll localted at C:\Program Files (x86)\Mindscape\WPF Elements\Bin. At this location, I also have the Mindscape.WpfElements.WpfElementsCore.lic file, but I still get an error that says: A valid license cannot be granted for the type Mindscape.WpfElements.WpfElementsCore. Contact the manufacturer of the component for more information. But if I build without my xaml file in focus, it builds with no error and runs fine too. Problem is, I need access to my XAML file! Should I be referencing this .dll from another location? I tried copying the C:\Program Files (x86)\Mindscape\WPF Elements\Bin to the root of C to no avail. |
|
|
|
|
Hello Thanks for these details. Just to clarify: When you have a xaml file open and focused in a tab in visual studio, then trying to run it causes a compile-time error with that message. But if you focus on a non-xaml tab in visual studio, then it compiles and runs fine. I've never heard of this scenario before, sounds like it could be a bug in Visual Studio. I have tried to reproduce this in all version from VS 2008 to VS 2013 but everything seems to work fine. What version of Visual Studio are you using? If you open the Sample Explorer application in Visual Studio and focus on one of its xaml files, does the problem still occur? If you open your project in a different version of Visual Studio and focus on a xaml file, does the problem still occur? Referencing the WPF Elements dll from the install directory is fine - this makes it easier to install nightly builds and not need to worry about moving the dll and lic each time. -Jason Fauchelle |
|
|
|
|
Hi, This may or may not be of any help, but since I have experienced a very similar problem I thought I would mention what I think I have learned. I find that this particular error message can happen at design time if you have installed an updated nightly build, and any of the projects are referencing a WpfElements dll from an earlier nightly build, or a dll I built from the source code. I find that this can happen inadvertently because when Visual Studio (I use VS 2010) cannot find a dll in a reference for whatever reason it may change the reference to another version of the dll that it can find, such as from some output folder (this is a bad feature of VS if you ask me). Therefore I have found I can resolve this issue by checking the WpfElements reference in every project to make sure it references the dll from the correct location, and deleting are adding back those that are incorrect. Peter |
|
|
|
|
Another thing to look into if you have Re-Sharper installed, you need to delete the _ReSharper.ProjectName. I was having the same problem when I switch to reference to the source code instead of dll yesterday. Gordon |
|
|
|
|
Jason: Yes, that is correct! This prevents me from modifying an existing xaml file using drag and drop for Mindscape controls, this also shows me multiple errors around the Mindscape elements in the xaml. I am using Visual Studio 2010. On a laptop install with Visual Studio 2010 and Visual Studio 2012, everything works fine. Should I have a line for the Mindscape.WpfElements.WpfElementsCore in my license.licx file? gPeter: Thanks for your reply sir. I have removed and re-added a reference to each project in my solution that is using Mindscape jsy to make sure they are correct, but my error remians. Gordon999 I am not using reshaper, but thank you so much for your input!! |
|
|
|
|
I also am getting a license error for a Mindscape component that i am not even using: The invocation of the constructor on type 'Mindscape.WpfElements.DualSlider' that matches the specified binding constraints threw an exception. I am not even using a DualSlider anywhere in my entire solution. |
|
|
|
|
Hello You'll need at least one line in the licx file for any of our controls (or WpfElementsCore) to validate the license. We use WpfElementsCore in the licx files of all the samples. There is a DualSlider embedded in each axis of a chart control which should be why you're seeing this message. -Jason Fauchelle |
|
|
|
|
I was finally able to get everything working, after I uninstalled Visual Studio 2010 and Mindscape. Then I had to delete any registry keys and any traces of Mindscape tools everywhere on my system. After a reboot, I then installed Visual Studio 2010 and then rebooted before installing Mindscape. After one last reboot, I tried to load up my existing project and received the same error. Removing Mindscape controls and trying to add them from the toolbar would not work. So since I have been here numerous times before, I shut down Visual Studio, and restarted it and created a brand new WPF project. It let me add Mindscape controls and save the project. After this, I closed that solution and opened my problem solution and it finally worked!! This has been one hell of a ride, but at least I can work now. Thanks Jason for trying to find an answer to my problem. Ed |
|
|
|
|
Hello Ed Sorry that you went through so much to get this working, but it's great that the problem is solved now! -Jason Fauchelle |
|
|
|
