Merge pull request #4694 from syncfusion-content/CI-validation-hf/26.2

185291 - UG For Syncfusion License Key Validation Issuefix - hotfix

Author: christopherhirudayasamy

blazor/getting-started/license-key/CI-license-validation.md

@@ -25,7 +25,17 @@ The following section shows how to validate the Syncfusion license key in CI ser
 
 * Download and extract the LicenseKeyValidator.zip utility from the following link: [LicenseKeyValidator](https://s3.amazonaws.com/files2.syncfusion.com/Installs/LicenseKeyValidation/LicenseKeyValidator.zip).
 
-* Open the LicenseKeyValidation.ps1 PowerShell script in a text\code editor.
+* Open the LicenseKeyValidation.ps1 PowerShell script in a text\code editor as shown in the below example.
+
+{% tabs %}
+{% highlight c# tabtitle="PowerShell" %}
+# Replace the parameters with the desired platform, version, and actual license key.
+
+$result = & $PSScriptRoot"\LicenseKeyValidatorConsole.exe" /platform:"Blazor" /version:"26.2.4" /licensekey:"Your License Key"
+
+Write-Host $result
+{% endhighlight %}
+{% endtabs %}
 
 ![LicenseKeyValidation script](images/license-validation.png)
 
@@ -39,14 +49,14 @@ The following section shows how to validate the Syncfusion license key in CI ser
 
 ## Azure Pipelines (YAML)
 
-* Create a new [User-defined Variable](https://learn.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#user-defined-variables) named `LICENSE_VALIDATION` in Azure Pipeline. Use the path of the LicenseKeyValidation.ps1 script file as a value (e.g., D:\LicenseKeyValidator\LicenseKeyValidation.ps1).
+* Create a new [User-defined Variable](https://learn.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#user-defined-variables) 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 pipeline and execute the script to validate the license key. 
+* 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.
 
 {% tabs %}
-{% highlight c# tabtitle ="YAML" %}
+{% highlight c# tabtitle="YAML" %}
 pool:
   vmImage: 'windows-latest'
 
@@ -63,20 +73,20 @@ steps:
 
 ## Azure Pipelines (Classic)
 
-* Create a new [User-defined Variable](https://learn.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#user-defined-variables) named `LICENSE_VALIDATION` in Azure Pipeline. Use the path of the LicenseKeyValidation.ps1 script file as a value (e.g., D:\LicenseKeyValidator\LicenseKeyValidation.ps1).
+* Create a new [User-defined Variable](https://learn.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#user-defined-variables) 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 pipeline and execute the script to validate the license key. 
+* Include the PowerShell task in the pipeline and execute the script to validate the license key. 
 
 ![LicenseKeyValidation script](images/license-validation-classic.png)
 
 ## 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 Syncfusion license key in GitHub actions.
+The following example shows the syntax for validating the Syncfusion license key in GitHub actions.
 
 {% tabs %}
-{% highlight c# tabtitle ="YAML" %}
+{% highlight c# tabtitle="YAML" %}
   steps:
   - name: Syncfusion License Validation
     shell: pwsh
@@ -87,11 +97,11 @@ The following example shows the syntax for validating Syncfusion license key in
 
 ## Jenkins
 
-* Create a [Environment Variable](https://www.jenkins.io/doc/pipeline/tour/environment) named 'LICENSE_VALIDATION'. Use Use the path of the LicenseKeyValidation.ps1 script file as a value (e.g., D:\LicenseKeyValidator\LicenseKeyValidation.ps1).
+* Create an [Environment Variable](https://www.jenkins.io/doc/pipeline/tour/environment) 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 Syncfusion license key in Jenkins pipeline.
+The following example shows the syntax for validating the Syncfusion license key in the Jenkins pipeline.
 
 {% tabs %}
 {% highlight json %}
@@ -111,11 +121,11 @@ pipeline {
 {% endhighlight %}
 {% endtabs %}
 
-## Validate the License Key Using ValidateLicense() Method
+## 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 ValidateLicense("Platform.Blazor") method. This ensures that the license key is valid for the platform and version you are using. For reference please check the following example.
+* Once the license key is registered, it can be validated by using the ValidateLicense("Platform.Blazor") method. This ensures that the license key is valid for the platform and version you are using. For reference, please check the following example.
 
 {% tabs %}
 {% highlight c# %}
@@ -131,7 +141,7 @@ bool isValid = SyncfusionLicenseProvider.ValidateLicense(Platform.Blazor);
 
 ![LicenseKeyValidationMethod](images/license-validation-method.png)
 
-* If ValidateLicense() method returns true, registered license key is valid and can proceed with deployment.
+* If the ValidateLicense() method returns true, registered license key is valid and can proceed with deployment.
 
-* If 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. 
+* 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. 
 

blazor/getting-started/license-key/how-to-register-in-an-application.md

@@ -22,7 +22,7 @@ Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense("YOUR LICENSE KEY
 N> * 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.
 * Syncfusion license validation is done offline during application execution and does not require internet access.  Apps registered with a Syncfusion license key can be deployed on any system that does not have an internet connection.
 
-I> Syncfusion license keys can be validated during the Continuous Integration (CI) processes to ensure proper licensing and prevent licensing errors during deployment. Refer to the [CI License Validation] (https://blazor.syncfusion.com/documentation/getting-started/license-key/ci-license-validation) section for detailed instructions on how to implement it.
+I> Syncfusion license keys can be validated during the Continuous Integration (CI) processes to ensure proper licensing and prevent licensing errors during deployment. Refer to the [CI License Validation](https://blazor.syncfusion.com/documentation/getting-started/license-key/ci-license-validation) section for detailed instructions on how to implement it.
 
 ## Blazor Web App