Licence Protector supports any number of modules / features (= functionality you want to license) inside a license file. You define the modules in the project template.
To validate a module there is a complete set of commands which can retrieve or change any bit of a module information, e.g. module name, number of users, time limitation, activation status etc.
If your application is sold with one main module (a basic product the customer always have to buy) and several optional modules, the way a module is activated depends on the way you distribute the product and other parameters. The main module is always activated using a Serial Number and the command PrepareAndCheck.
• | If you are using an e-commerce system, send out keys manually (you sell only small volumes) or if you can rely on an online connection, you would send out an Activation Key which changes the module information in the license file, e.g. sets a yes/no module to yes or adds additional network licenses. The Activation Key is typically typed in using the License Viewer (or the command ApplyActivationKey) and no additional programming is necessary |
• | If you sell each single module with a separate CD or you cannot rely on an online connection and you sell large volumes youl, every module would be activated using a Serial Number. See: Activate each module with a Serial Number |
• | If your application has more than 5 modules a good approach is to deliver a license file + Serial Number |
• | If you can rely on an online connection, you can deliver by downloading the license file. Only one Serial Number / ID is used to download a customer specific license file with all the specific customer settings including multiple modules |
If you sell 2 versions of an product (e.g. Standard and Premium version) or a version with several modules but no main module, one of the following approaches could be used:
See also
Validate modules
Deliver license file + Serial Number
Activate each module with a Serial Number
Create Activation Keys