If you have 2 versions and the user can either buy a Standard or Premium version, then one implementation option is to use the following workflow.
Create a project template which includes both modules and set LoadAsDefault for only one module to true. This will load by default only this module in the License Generator. Each module has an own ModuleNumber which ensures, that a key for module 1 can not be used on module 2.

You could also make 2 different project files with different project encryption keys instead of one project file and 2 modules. This is mandatory if each product has additional modules.
|
Now generate 2 license files. One which contains the Standard Version and one which contains the Premium Version.
Start the License Generator. The default module will load. Save a license file as standard.lic. Then change the standard module. Click in the list on the description of the module. A listbox will appear where you can select the Premium Version module. Save a license file as premium.lic.

|
The installer includes both license files (standard.lic and premium.lic). When the user downloads a trial version he can select which version he likes to install. Depending on the version you copy either the premium.lic or standard.lic.

Instead of selecting the product during the installation process, you could install both license files (with different names) and let the user select the product within the application. Just open the license file which belongs to the selected application.
|
Depending on the available license file, you start the application using EasyGo either with the module number for Standard or Premium version in the command PrepareandCheck.
Install the version on separate directories e.g. ..\programs\xy Standard and programs\xy Premium
As each license file has an own license file ID, the user has the full evaluation time for both versions, e.g. 15 days for Standard version and 15 days for Premium version
|
If you want to use only one license file instead of 2 different files, you could use GetModuleList to retrieve the module number, which is used in the license file. The module number defines, if it is a Standard or Premium Version.