The IntelliLock license system allows you to distribute your assembly without a license file provided that you have set "Run Without Valid License" to True. When your customer purchases a license, you use the License Generator or the SDK to build a license file to unlock your assembly. Lock settings in a license file always override settings which are stored in the assembly.
To create a valid license file, the same master key must be used for license creation as was used to lock your assembly. This master key is generated when you create your project, which must be saved to preserve the original key, otherwise you will be unable to generate valid license files.
Hardware Lock License - This option allows you to create licenses which can be used only on a particular PC, based on a Hardware ID which identifies the particular combination of hardware in that PC. License Files which have the Hardware disabled can be used on any PC. Utilising the Hardware Lock prevents your customer from purchasing one license file and using it on multiple PCs. To create licenses which are locked to the hardware of a particular PC, you must enable "Hardware Lock" and provide the Hardware ID of the client's PC. Please use the SDK function to display the Hardware ID from within your assembly (for example in the "About" dialog box).
Tolerance Level - The tolerance level represents the number of hardware components allowed to be changed before the Hardware ID is recognized as invalid by your locked assembly.
Check Hardware ID At Design Time Only - Restricts the design-time usage to a specific machine. Useful for component libraries.
Runtime License - The generated license is valid during runtime.
Design-Time License - The generated license is valid during design-time by a visual designer or the compiler.
Version Lock - Check this option to ensure the license is only valid to a specific assembly version. Use an asterisk (*) to define which parts of the version number should be ignored. Click with the right mouse button on the 'License Information' list to define further assembly restrictions.
Apply Trial Restrictions To License File - This option locks the license file with the settings you set in tab "Lock Settings". Use it to extend trial periods, accomplish subscription/time based license expiration etc...
As Trial Version - If you check this option the created license file applies trial restrictions (based on the settings you set in tab "Lock Settings") to your assembly. Useful to apply or extend trial periods.
As Full Version - If you check this option the created license file uses the settings you set in tab "Lock Settings" to apply a time limited full version to your assembly.
New Period - If you check this option the created license file uses an independent data slot to store exceeded days etc. Leave this unchecked to reuse already exceeded days ect.
Force License Server Validation - If you want to validate a license file via a server first before it is recognized as a valid license file, you can set the address to the corresponding web service here. Use the Menu/Bar item "License Management"->"ASP.NET Management/Activation" to create the corresponding service.
Floating License / Concurrent User - If you want to appy a floating license which is controlled via server you can set the address to the corresponding web service here. Use the Menu/Bar item "License Management"->"ASP.NET Management/Activation" to create the corresponding service.
License Information - You can add custom license information to the license file. Custom license information allows a flexible license shema, modular licensing etc.. Your assembly can access this information with the functions available in the SDK libraries. Use the right mouse button to add assembly attribute information. Your locked assembly automatically compares this special information with the attributes of the calling assemblies. Only an assembly with matching attributes is allowed to access your locked assembly.
