Each successive launch validates the license on that computer. On the first launch, an Activation dialog is presented to accept an Activation Code. On each launch, your application communicates with the runtime file. With this approach, the Ticket and QuickLicense runtime are embedded within your protect application so you distribute just one file to customers. The Ticket file and royalty-free runtime file are distributed with the protected application.Īlternatively, use AddLicense to wrap an application with the protective license without programming. This binds your application to the Ticket file that defines your license. To protect an application, call QuickLicense runtime from your program with a programming interface (API) command. It discourages users from distributing your software to unlicensed users since that would require giving out their uniquely identifiable Name and Activation Code. This approach is less secure, but gives the user the flexible to activate on several machines with the same Name/Code pair. The license can auto-activate on first launch or required a unique Activation Code for each computer.Īlternatively, the Activation dialog can show a Name and Activation Code field.
License configuration takes just minutes and gives the developer many options to choose from. QuickLicense is used to configure a Ticket file that defines how the license and activation process works.
