Licensing .NET Applications

This topic describes how ComponentOne licensing is applied to modern .NET applications, including .NET Core, ASP.NET Core, WinForms, WPF, Blazor, MAUI, and WinUI.

For other application types and scenarios, see Licensing Applications.

How Licensing Works for .NET Applications

ComponentOne controls support application licensing through NuGet package build scripts and supporting licensing tools.

Each developer machine or build machine that builds the application must have an activated serial key. Licensing is applied automatically during the build process.

For instructions on activating a serial key, see Activating a Serial Key.

Runtime License Generation

When an application is built on a properly activated machine:

• A runtime license file (.sa3licx) is generated automatically during the build.

• The license file is embedded in the application as an embedded resource.

For modern .NET applications, the generated runtime license file uses the .sa3licx format.

In some mixed or compatibility scenarios, a legacy runtime license file (.gclicx) may also be generated.

Before embedding, the license file can typically be found in the build output directory, for example:

• obj/Debug

• obj/Release

The embedded runtime license file must be included when the application is distributed.