Protect a C# app with the QLM License Wizard standalone executable

Following is a step-by-step procedure to protect a C# application by using the QLM License Wizard Standalone application. Note that the steps below assume you have a QLM License Server already setup.

1. Launch the QLM Management Console

2. Create a product from the β€œDefine Product” tab or use the Demo 1.0 product if you are evaluating QLM.

3. Go to the "Protect your application" tab:

  • Page 1: Select the product to protect and the License Server

  • Page 2: Select C#

  • Page 3: Leave the default settings or customize the look & feel if needed. By default, QLM will bind the license to the Computer Name. You can select the binding of your choice by setting the QlmLicenseBinding property located in the section "6. Qlm License Properties".

  • Page 4a: Select the folder where your source code is located and click Save

  • Page 4b: Click Update Visual Studio Project and locate your *.csproj. If this step fails, just skip it.

  • Page 5: Click Finish

The "Protect your application" should have generated a class file called LicenseValidator.cs and an XML file that contains your customizations. In this guide, we will assume the XML file is called "Demo 1.0.lw.xml" which should be the case if you are evaluating QLM.

  • Open your Visual Studio project

  • If the Visual Studio integration above succeeded, confirm that the following was added to your project:

    • A reference to QlmLicenseLib.dll

    • A new file called LicenseValidator.cs

    • A new file called Demo 1.0.lw.xml

    • Copy

  • If the Visual Studio integration did not work, do the following:

    • Add a reference to C:\Program Files\Soraco\QuickLicenseMgr\Redistrib\net?.0\QlmLicenseLib.dll

    • Add the file LicenseValidator.cs to your project

    • Add the file Demo 1.0.lw.xml to your project and set the property "Copy to Output Directory" to "Copy if newer"

    • Copy C:\Program Files\Soraco\QuickLicenseMgr\Redistrib\net?.0\QlmLicenseWizard.exe to your bin folder.

  • You will now need to update your application to add the license validation code.

  • Add the following statement to your main module: using QlmLicenseLib

  • Define the following global variables:

static QLM.LicenseValidator lv; static string settingsFile; static string wizardExec;

  • Copy and paste the code below into your application

static void ValidateLicense ()
    System.Reflection.Assembly thisAssembly =                System.Reflection.Assembly.GetExecutingAssembly();
    string location = System.IO.Path.GetDirectoryName(thisAssembly.Location);
    settingsFile = System.IO.Path.Combine(location, "Demo 1.0.lw.xml");
    wizardExec = System.IO.Path.Combine(location, "QlmLicenseWizard.exe");
    lv = new QLM.LicenseValidator(settingsFile);
    bool needsActivation = false;
    string errorMsg = string.Empty;
    ELicenseBinding licenseBinding = ELicenseBinding.ComputerName;
    if (lv.ValidateLicenseAtStartup(licenseBinding, ref needsActivation, ref errorMsg) == false)
        int exitCode = DisplayLicenseForm();
        if (exitCode == 4)
        if (lv.ValidateLicenseAtStartup(licenseBinding, ref needsActivation, ref errorMsg) == false)
static private int DisplayLicenseForm()
    string errorMessage;
    if (lv.QlmLicenseObject.ValidateSettingsFile(settingsFile, out errorMessage) == false)
        return 0;
    string args = String.Format("/settings \"{0}\"", settingsFile);
    if (!System.IO.File.Exists (wizardExec))
        wizardExec = @"C:\Program Files\Soraco\QuickLicenseMgr\QlmLicenseWizard.exe";
    return lv.QlmLicenseObject.LaunchProcess(wizardExec, args, true, true);

Now in your application's startup code, call ValidateLicense().

This completes the integration.

To generate a license key for testing purposes:

  • Go to the Manage Keys tab.

  • Click "Create Activation Key"

  • Select the Product (Demo 1.0 for trials) and click OK.

  • Copy and Paste the generated Activation Key in the License Wizard launched when your application starts up and follow the steps in the wizard.

For information about which files need to be deployed with your application, refer to this article.

Last updated