Licensing woes

Topics related to the Krypton Navigator.

Moderators: Phil Wright, Chris Porter

Licensing woes

Postby mattman206 » Wed Oct 03, 2007 7:26 am

Hello,

I just upgraded from 2.6.0 to 2.6.1 and now my license key does not work. Every time I build, it asks me for the key, I paste it in, and it finishes compiling....but then when I run my program it pops up a nasty message box saying that it was built with an unlicensed Krypton Navigator.

I made sure to save the "ComponentFactory.Krypton.Navigator.KryptonNavigator.lic" file with my license key in it (it worked before).

I tried uninstalling and reinstalling 2.6.1 and it still doesn't like it. What am I doing wrong? I've wasted a lot of time trying to update to 2.6.1.

Thanks,
-Matt
mattman206
 
Posts: 8
Joined: Tue Feb 27, 2007 2:04 pm

Postby Phil Wright » Wed Oct 03, 2007 5:46 pm

Please use the following steps...

• Open the project and remove references to Krypton assemblies
• Perform uninstall of Krypton
• Search machine for ‘ComponentFactory.*.dll’ and remove all matches
• Install Krypton Toolkit 2.6.1
• Open project and add references to Krypton assemblies
• Perform rebuild and enter serial key if asked
• If it does not ask, then set clock forward 31 days and rebuild again
(remember to set clock back 31 days afterwards!)

That should ensure you only have the latest version of the assemblies on your machine and so when asked for the license it is expecting the 2.6 valid serial key.

If that still does not work then you should check to ensure that there is a .licx file in your project with an entry referring to the Navigator/Ribbon control. The .licx file is used to determine which licenses are embedded in the built application. Note that you need to use the 'Show All Files' option on your solution as the .licx file is hidden by default inside the Properties folder.

You can drag and drop a new instance of the Navigator/Ribbon onto your application, and then just remove it again, to force the creation of the .licx file.

Let me know how you get on
Phil Wright
Site Admin
 
Posts: 2720
Joined: Thu Apr 13, 2006 2:55 pm
Location: Melbourne, Australia

Postby mattman206 » Thu Oct 04, 2007 12:12 am

Hi Phil,

I've already done all of that, and did it again just to be sure. I even removed all Krypton controls from my toolbox and started from scratch.

The only ComponentFactory* DLLs are in "C:\Program Files\Krypton 2.6.1\" and "C:\Program Files\Krypton 2.6.1\PublisherSigned". I am using the PublisherSigned ones.

I copied these DLLs to my SVN repository as /trunk/Shared/Libs/ComponentFactory*.dll

There is a licx in my Properties folder with the following line:
ComponentFactory.Krypton.Navigator.KryptonNavigator, ComponentFactory.Krypton.Navigator, Version=2.6.1.0, Culture=neutral, PublicKeyToken=a87e673e9ecb6e8e

I removed all of the references to the DLLs, closed the solution, reopened, and re-added them. It asked me for my license and I pasted it in.

I opened up Sysinternal's FileMonitor while building and even watched to make sure that the .licx file was being read, and it was. lc.exe was called in there as well.

I can open up my compiled EXE with .NET Reflector and see there is a resource with <program name>.exe.licenses. It has a binary blob with the Krypton Navigator assembly name in it, 2.6.1 as expected. There is a long string at the end that looks like my keycode but doesn't match.

Even after all of that, it still says I am using an unlicensed copy when I start the program.

I've wasted 8-9 hours trying to get this stupid thing to work. Maybe I'll just go back to 2.6.0...

I'm at a loss on what to do now.

-Matt
mattman206
 
Posts: 8
Joined: Tue Feb 27, 2007 2:04 pm

Postby mattman206 » Thu Oct 04, 2007 1:10 am

Perhaps I am not using the correct license key.

Could you resend the license key? I'll privately email you with the information.

Thanks,
-Matt
mattman206
 
Posts: 8
Joined: Tue Feb 27, 2007 2:04 pm

Postby mattman206 » Thu Oct 04, 2007 1:32 am

Hi Phil,

Thanks for re-sending the key. That was the problem!

I think that there was some very strange behavior going on because (for whatever reason) 2.5.1 wasn't fully installed, and the license compiler let me use 2.6.0 with a 2.5.1 key. But when I updated to 2.6.1, I fully removed 2.5.1 and that's what broke it. Very strange indeed. Gotta love unintended consequences.

Thanks again for the prompt reply. The support for Component Factory products is excellent.

-Matt
mattman206
 
Posts: 8
Joined: Tue Feb 27, 2007 2:04 pm

Identical License Issue

Postby Jim_F » Wed Oct 31, 2007 3:29 am

Good morning

I read this topic over and over again and am faced with the exact same issue, however I do have the new license key. After reviewing all the posts above, I have done everything twice and the licx that gets generated in design time is still reading this, "ComponentFactory.Krypton.Navigator.KryptonNavigator, ComponentFactory.Krypton.Navigator, Version=2.6.1.0, Culture=neutral, PublicKeyToken=a87e673e9ecb6e8e".

I've gone into the C:\Program Files\Component Factory Pty Ltd\Krypton Navigator 2.6.1\Bin\PublisherSigned and reviewed the contents of ComponentFactory.Krypton.Navigator.KryptonNavigator.lic and it has the new license key within it.

What am I doing wrong and how is the licx being generated?

Thanks in advance.

Jim
Jim_F
 
Posts: 2
Joined: Wed Oct 31, 2007 3:25 am

Postby Phil Wright » Wed Oct 31, 2007 3:45 am

Try doing a search for all .lic files on your machine. Ensure that all the krypton ones have the correct new licence in them. It might be that your project is referencing to a different instance of the assembly than you think. If so then please email me directly with the licence that you are using, I can check it to ensure it is correct for the version you have installed. My email is...

phil.wright@componentfactory.com
Phil Wright
Site Admin
 
Posts: 2720
Joined: Thu Apr 13, 2006 2:55 pm
Location: Melbourne, Australia


Return to Krypton Navigator

Who is online

Users browsing this forum: No registered users and 0 guests