[]
DOCS DEMOS BLOGS SUPPORT PRICING EULA
(Showing Draft Content)

Create a Runtime License

When an application is built on a properly activated development or build machine, the MESCIUS runtime license file is generated and embedded automatically into the application.

Depending on the licensing system used, the runtime license file is created in one of the following formats:

  • .sa3licx

  • .gclicx (GCLM licensing)

In some scenarios, you may need to generate the runtime license manually. This typically applies to projects such as user controls or class libraries, where the runtime license is not generated automatically. A unique runtime license file must be created for each application name.

Generate a Runtime License Using Visual Studio

To manually generate a runtime license file using the MESCIUS License Manager:

  1. Open the application in Visual Studio where the license needs to be embedded.

  2. From the Tools menu, select MESCIUS > MESCIUS License Manager.

  3. Click Create Runtime License.

  4. Select the project that requires the license file.

  5. Click Generate.

After the process is completed, , the generated runtime license file (.sa3licx or .gclicx) is automatically added to the project as an embedded resource.

Generate a Runtime License Using the Command Line

You can also generate a runtime license file using command-line tools, depending on the licensing system.

MESCIUS License Manager

Use the SA3 client to generate a .sa3licx file:

sa3client lc -p "{product}" -f "{feature}" -t "{appName}" -o "{outputFile}"

Parameters:

  • -p → Product (e.g., C1S, C1P)

  • -f → Feature (edition/framework)

  • -t → Application name (e.g., MyApp)

  • -o → Output file path (e.g., C:\Downloads\MyAppFolder)

During this process:

  • A .sa3licx file is generated.

  • Add the file to your project (for example, in the Properties folder).

  • Set the Build Action to EmbeddedResource.

Product and Feature Mapping

The following table lists common product types and corresponding feature identifiers:

Product

Edition

Features

Versions

  • ComponentOne Subscription (C1S)

  • ComponentOne Perpetual (C1P)

  • Studio Enterprise Edition

  • Extended Trial Edition

  • Built-in Trial Edition

  • Studio Enterprise

  • se

  • v2025.1

  • v2025.2

  • v2026.1

  • …

  • WinForms Edition

  • winform

  • . NET MAUI Edition

  • maui

  • ASP. NET MVC Edition

  •  

  • aspmvc

  • ASP. NET Core Edition

  • aspcore

  • Blazor Edition

  • blazor

  • WPF Edition

  • wpf

  • WinUI Edition

  • winui

  • Data Service Edition

  • WinForms Data Service Edition

  • datasvc

These values are used in combination with the -p and -f parameters during command-line license generation.

GCLM Licensing

Use the gclm tool to generate a .gclicx file:

Windows:

gclm.exe "product-id" -lc ./.gclicx "app-name"

Linux/Mac:

gclm "product-id" -lc ./.gclicx "app-name"

Note:

  • On Windows, the generated .gclicx file is created in:

    C:\ProgramData\GrapeCity\gclm

  • Add the generated file to your project (for example, in the Properties folder).

  • Set the Build Action to EmbeddedResource.

Runtime License File Behavior

For both .sa3licx and .gclicx:

  • The runtime license file is generated specifically for the application being built.

  • The file must be embedded as a resource in the project.

  • Each application requires its own unique runtime license file.

See Also