Licensing .NET Applications

This topic applies to licensing .NET Core, ASP.NET Core, .NET 5, .NET 6+ (WinForms, WPF), Blazor, UWP, MAUI, and WinUI applications. For more options, see Licensing Applications.

ComponentOne controls support application licensing through the NuGet package build scripts. Each developer or build machine needs an activated serial key to build the project and properly license the application. To activate a serial key, see Activating a Serial Key.

When the application is built on a properly activated machine a unique runtime license file (.gclicx) is generated and embedded with the application. The license file can be found in the build output (obj/Debug or obj/Release). This file must be distributed with the application as an embedded resource.

Notes:

• The automatically generated license file (.gclicx) requires that the application name matches the project in which it's built. If you need to license an application with a different name (such as when building a user control), see Licensing User Controls.
• The NuGet package licensing is only supported in Visual Studio 2019 and above. For older versions of Visual Studio, see Licensing .NET Framework Applications.