LicenseID, DLL and Targets

User Guide ››
Parent Previous Next

LicenseID, DLL and Targets.

This chapter describe:

The tools for these tasks are located in the License Menu. They are also directly accessible from the Start Page without the need of opening a project.

This chapter also describe

These tasks are primarily accomplished using the Target Manager tool located in the Compile Menu but are described here, because the concept of Single Target Compilation is closely related to your license file and your public private key pairs.

File Administration.

SCRAMBLECODE uses two very important files to store license information and registered key pairs:

Each serial number you purchase will be used to create these two files as described here. The files are crucial for a developer in order to create your customized VM DLL files with your public key embedded, or to perform Single Target Compilation of bytecode to be executed by your VM DLL.

To inform SCRAMBLECODE about, where to find these files, the developer can create target definitions using the Target Manager tool. This tool allows the developer a great deal of freedom to manage most of the involved files in any directory structure desired.

However, the following rules apply:

The reason for these rules are, that it should be easy and straight forward for an administrator to create/update license and key files on a separate computer without having to setup any target definitions first. Furthermore these restrictions make the administrative process less susceptible to errors or misunderstandings.


Private Key Considerations.

If you administer a multiuser license with access to a number of keys, you should consider using Private Key Protection by applying a password to encrypt all private keys in the file "PrivateKey.txt".

If some keys are not used by all development teams, you may remove certain key sections in a copy of the file, before deploying the file internally within your organization. These "reduced" PrivateKey files can also be given different passwords.


Always keep a backup of the original, complete and unprotected file "PrivateKey.txt" in a safe and secure manner. If you forget the password for a protected version of the file, you will need to use the original unprotected file to create a new protected version. A forgotten password can't be reconstructed and is not saved anywhere. The same applies for deleting key sections within the PrivateKey file, as a deleted private key can't be reconstructed and is not saved anywhere.