Syncfusion license key validation in CI services

26 Sep 20247 minutes to read

Syncfusion license key validation in CI services ensures that Syncfusion Essential Studio components are properly licensed during CI processes. Validating the license key at the CI level can prevent licensing errors during deployment. Set up the continuous integration process to fail in case the license key validation fails. Validate the passed parameters and the registered license key again to resolve the issue.

The following section shows how to validate the Syncfusion license key in CI services.

Download and extract the LicenseKeyValidator.zip utility from the following link: LicenseKeyValidator.
Open the LicenseKeyValidation.ps1 PowerShell script in a text\code editor as shown in the below example.

PowerShell
# Replace the parameters with the desired platform, version, and actual license key.

$result = & $PSScriptRoot"\LicenseKeyValidatorConsole.exe" /platform:"WPF" /version:"26.2.4" /licensekey:"Your License Key"

Write-Host $result

LicenseKeyValidation script

Update the parameters in the LicenseKeyValidation.ps1 script file as described below.

Platform: Modify the value for /platform: to the desired platform. For reference, please check the applicable example platforms below.

(e.g., “WindowsForms”, “WPF”, “WinUI”, “UWP”, “MAUI”, “Xamarin”, “Blazor”, “FileFormats”)

Version: Change the value for /version: to the required version (e.g., “26.2.4”).

License Key: Replace the value for /licensekey: with your actual license key (e.g., “Your License Key”).

NOTE

This feature is available only for the following Syncfusion Essential Studio platforms starting from version 16.2.0.41: WPF, Windows Forms, WinUI, UWP, MAUI, Xamarin, Blazor, FileFormats.

Azure Pipelines (YAML)

Create a new User-defined Variable named LICENSE_VALIDATION in the Azure Pipeline. Use the path of the LicenseKeyValidation.ps1 script file as a value (e.g., D:\LicenseKeyValidator\LicenseKeyValidation.ps1).
Integrate the PowerShell task in the pipeline and execute the script to validate the license key.

The following example shows the syntax for Windows build agents.

YAML
pool:
  vmImage: 'windows-latest'

steps:

- task: PowerShell@2
  inputs:
    targetType: filePath
    filePath: $(LICENSE_VALIDATION) #Or the actual path to the LicenseKeyValidation.ps1 script.
  
  displayName: Syncfusion License Validation

Azure Pipelines (Classic)

Create a new User-defined Variable named LICENSE_VALIDATION in the Azure Pipeline. Use the path of the LicenseKeyValidation.ps1 script file as a value (e.g., D:\LicenseKeyValidator\LicenseKeyValidation.ps1).
Include the PowerShell task in the pipeline and execute the script to validate the license key.

LicenseKeyValidation script

GitHub actions

To execute the script in PowerShell as part of a GitHub Actions workflow, include a step in the configuration file and update the path of the LicenseKeyValidation.ps1 script file (e.g., D:\LicenseKeyValidator\LicenseKeyValidation.ps1).

The following example shows the syntax for validating the Syncfusion license key in GitHub actions.

YAML
steps:
  - name: Syncfusion License Validation
    shell: pwsh
    run: |
	  ./path/LicenseKeyValidator/LicenseKeyValidation.ps1

Jenkins

Create an Environment Variable named ‘LICENSE_VALIDATION’. Use the path of the LicenseKeyValidation.ps1 script file as a value (e.g., D:\LicenseKeyValidator\LicenseKeyValidation.ps1).
Include a stage in Jenkins to execute the LicenseKeyValidation.ps1 script in PowerShell.

The following example shows the syntax for validating the Syncfusion license key in the Jenkins pipeline.

JSON
pipeline {
	agent any
	environment {
		LICENSE_VALIDATION = 'path\\to\\LicenseKeyValidator\\LicenseKeyValidation.ps1'
	}
	stages {
		stage('Syncfusion License Validation') {
			steps {
				sh 'pwsh ${LICENSE_VALIDATION}'
			}
		}
	}
}

Validate the License Key By Using the ValidateLicense() Method

Register the license key properly by calling RegisterLicense(“License Key”) method with the license key.
Once the license key is registered, it can be validated by using the ValidateLicense(“Platform.WPF”) method. This ensures that the license key is valid for the platform and version you are using. For reference, please check the following example.

C#
using Syncfusion.Licensing;

//Register Syncfusion license key 
Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense("YOUR LICENSE KEY");

//Validate the registered license key
bool isValid = SyncfusionLicenseProvider.ValidateLicense(Platform.WPF);

LicenseKeyValidationMethod

NOTE

Followings are the applicable list of platforms that can be passed to the ValidateLicense method WindowsForms, WPF, ASPNETCore, ASPNETMVC, FileFormats, Xamarin, UWP, ASPNET, Blazor, WinUI, MAUI.

If the ValidateLicense() method returns true, registered license key is valid and can proceed with deployment.
If the ValidateLicense() method returns false, there will be invalid license errors in deployment due to either an invalid license key or an incorrect assembly or package version that is referenced in the project. Please ensure that all the referenced Syncfusion assemblies or NuGet packages are all on the same version as the license key’s version before deployment.

Validate the License Key By Using the Unit Test Project

To create a unit test project in Visual Studio, choose File -> New -> Project from the menu. This opens a new dialog for creating a new project. Filtering the project type by Test or typing Test as a keyword in the search option can help you to find available unit test projects. Select the appropriate test framework (such as MSTest, NUnit, or xUnit) that best suits your need.

Unit Test Projects

For more details on creating unit test projects in Visual Studio, refer to the Getting Started with Unit Testing guide.
Register the license key by calling the RegisterLicense(“Your License Key”) method with the license key in the unit test project.

NOTE

Place the license key between double quotes. Also, ensure that Syncfusion.Licensing.dll is referenced in your project where the license key is being registered.

Once the license key is registered, it can be validated by using the ValidateLicense(“Platform.WPF”, out var validationMessage) method. This ensures that the license key is valid for the platform and version you are using.
For reference, please check the following example that demonstrates how to register and validate the license key in the unit test project.

C#
public void TestSyncfusionWPFLicense()
{
	var platform = Platform.WPF;
	// Register the Syncfusion license key
	SyncfusionLicenseProvider.RegisterLicense("Your License Key");

	bool isValidLicense = SyncfusionLicenseProvider.ValidateLicense(platform, out var validationMessage);
	Assert.That(isValidLicense, Is.True, $"Validation failed for {platform}." + $" Validation Message: {validationMessage}");

	// Log validation messages to TestContext output
	if (isValidLicense)
	{
		TestContext.Out.WriteLine($"Platform {platform} is correctly licensed for version " + $"{typeof(SyncfusionLicenseProvider).Assembly.GetName().Version}");
	}
}

Once the unit test is executed, if the license key validation passes for the specified platform, the output similar to the following will be displayed in the Test Explorer window.

License Validation Success Message

If the license validation fails during unit testing, the following output will be displayed in the Test Explorer window.

License Validation Failure Message

License validation fails due to either an invalid license key or an incorrect assembly or package version that is referenced in the project. In such cases, verify that you are using the valid license key for the platform, and ensure the assembly or package versions referenced in the project match the version of the license key.