Phil Wright wrote: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.
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.
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.
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.