License problem

[Riccardo]

I'm using an obfuscator that creates a native image of my assembly and that seem to make impossibile to validate the license to the krypton dlls.
What i can try to do?

[Phil Wright]

Does your utility allow some resources to be excluded from the process? You need to prevent the licenses resourse from being modified.

[Riccardo]

No, my utility don't make me select a resource to not be modified.
I've already thinked to preserve the "assemblename.license" resource by encrypting/obfuscation, but it is impossible with my utility,

[Phil Wright]

Then your own choice is to compile the source code version of the product so that you no longer have any license checking taking place.

[Chris Porter]

Then your own choice is to compile the source code version of the product so that you no longer have any license checking taking place.

This is the best "feature" of owning the source code in my opinion. I love being able to see exactly what/how Phil is doing under the covers of the toolkit, but for productivity, being able to deploy apps without license concerns has definitely made my life easier.

[Riccardo]

How can obtain the sources?

[Chris Porter]

When you purchase a license for the Navigator/Ribbon/Workspace/Suite you can choose to pay a bit extra to get the source:
http://www.componentfactory.com/purchase.php

If you have already purchased one or more of these components and didn't purchase the source, I would suggest you contact Phil through email to discuss your options: sales@componentfactory.com.

[fitzsic]

I have the source, compiled and shipped with my application.
My exe is encrypted to stop recompilation.
On some user machines, my program works, on others the license screen appears asking them to contact the software supplier.
From previous posts, it says to just compile the source to stop the license screen appearing. This does not seem to be a 100% answer.
Please can you let us know how we can modify the source to stop this problem from keep happening. It’s getting frustrating to keep refunding people.

[Phil Wright]

You must be distributing the wrong copy of the assemblies because the source code does not contain any license checking or a dialog to warn that an application is not licensed. So if you distribute the correct copy of the assembly then it is impossible to get a license error. Once you compile the source code you need to copy the built assemblies into your project for use.

[Chris Porter]

Phil is correct, in the source code version of the Suite there is no licensing code included. Compiling from source will result in an assembly that will not (and cannot) prompt the user for a license. My bet is that the users getting the prompt where either given the wrong assembly or had Krypton previously installed and GAC'd.