Products
PDFKit.NET 5.0
Created
3/6/2018
Tags
Licensing

Supported licenses

Server license

The Server license is based on the NETBIOS name and this continues to work unchanged with the .NET Standard build. We use Environment.MachineName to determine the NETBIOS name at runtime.

Client Application license

For the builds other than .NET Standard, we verify the license key against the Company and Product assembly attribute of the entry assembly (EXE). This license type is still supported with the .NET Standard build but behaves differently.

Because the entry assembly cannot be determined uniformly across all supported platforms, the .NET Standard build determines the entry assembly as the innermost calling assembly that has a TallComponents license assembly attribute. Note this this requires you to register the license key as a TallComponents license assembly attribute.

Web Application license

This license type verifies the license key against the Company and Product assembly attribute of the calling assembly and this is supported.

The calling assembly is determined as the innermost calling assembly that has a TallComponents license assembly attribute. Note this this requires you to register the license key as a TallComponents license assembly attribute.

Client Component license

This license type verifies the license key against the Company and Product assembly attribute of the calling assembly and this is supported with the .NET Standard build.

The calling assembly is determined as the innermost calling assembly that has a TallComponents license assembly attribute. Note this this requires you to register the license key as a TallComponents license assembly attribute.

Unsupported licenses

ASP.NET Domain license

This license type is not supported by the .NET Standard build because HttpContext.Current does not exist anymore in ASP.NET Core.

Windows Domain license

This license type is not supported by the .NET Standard build because it is Windows specific.