Crypto Obfuscator - Common Licensing Issues

Q. After obfuscation, why do I get the following error message: "Assemblies obfuscated using evaluation version of Crypto Obfuscator will stop working on <date>" ?

This happens if Crypto Obfuscator is running in evaluation mode. If you are a licensed user, enter the license code for Crypto Obfuscator that you received from us when you purchased the product.

If you have entered the license, but still get this message, its most likely that Crypto Obfuscator is unable to read the license code which is stored in the registry. To prevent this, ensure that Crypto Obfuscator is running under the same user account in which you entered the license.

Q. When I tried to use my existing license code with a new version. I get a "Signature Invalid" message.

This most likely happens when you try to use a license code for one version of Crypto Obfuscator with another version. This won't work because each version of Crypto Obfuscator requires its own license code. If you have a license with an active Support And Upgrade Subscription, then you can request a free license for the new version from http://www.ssware.com/upgrade.htm

If you do not have the Support And Upgrade Subscription you can upgrade to the latest version at a discount to the full price. To upgrade, goto http://www.ssware.com/upgrade.htm

If your Support And Upgrade Subscription has lapsed, you can make the subscription current and renew it. To do this, goto http://www.ssware.com/upgrade.htm

Q. I get one of the following messages when I obfuscate via by build process, but I do not get this message when I obfuscate via the Crypto Obfuscator UI:

'Your evaluation of Crypto Obfuscator has expired'
"Assemblies obfuscated using evaluation version of Crypto Obfuscator will stop working on <date>"

Its most likely that Crypto Obfuscator is unable to read the license code which is stored in the registry. To prevent this, ensure that Crypto Obfuscator is running under the same user account in which you entered the license.

If the user account under which Crypto Obfuscator runs is not under your control, then you can explicitly specify the license code when invoking Crypto Obfuscator as follows:

When obfuscating via the co.exe command-line tool:

Add the

licensecode=<your-license-code>

parameter to the command-line passed to co.exe. For example:

co.exe projectfile=myproject.obproj licensecode=mylicensecode

Additionally, you can pass the checkfulllicense=true parameter which causes co.exe to fail if it is running under evaluation mode.

When obfuscating via MSBuild integration:

Open your csproj files and add the <CO_LC> node before the <CO_Config> node as follows:

<CO_LC>your-license-code</CO_LC>
<CO_Config>....</CO_Config>
....

Additionally you can also specify the

<CO_CheckFullLicense>True</CO_CheckFullLicense>

node which causes Crypto Obfuscator to fail if it is running under evaluation mode.

Q. Certain obfuscation features are not working in the licensed version, but they were working in the trial version.

Its possible that you purchased the Standard or Professional Edition and the specific obfuscation feature is not present in that edition. See http://www.ssware.com/cryptoobfuscator/compare.htm for a detailed comparison of the editions. To upgrade to a higher edition, goto http://www.ssware.com/upgrade.htm

The reason the feature worked in the trial version is because the trial version works as a fully functional Enterprise Edition license and so all the features are enabled in the trial version.