|
Syncfusion.Pdf.Base.dll |
@@ -123,11 +124,11 @@ WPF Spreadsheet control can be added to an application either through the design
{% tabcontent Via Designer %}
-1. Add the theme and the [SfSkinManager](https://help.syncfusion.com/cr/wpf/Syncfusion.SfSkinManager.html) namespace to style the control correctly. Then, include the SfSkinManager namespace in the XAML code and apply the desired theme.
+1. Add the theme and the [SfSkinManager](https://help.syncfusion.com/cr/wpf/Syncfusion.SfSkinManager.html) namespace to style the control correctly. Include the SfSkinManager namespace in the XAML code and apply the desired theme.
{% tabs %}
{% highlight xaml tabtitle="MainWindow.xaml" %}
-® Controls tab, and find the SfSpreadsheet/SfSpreadsheetRibbon toolbox items.
+2. Open the Visual Studio **Toolbox**. Navigate to the Syncfusion® Controls tab and find the `SfSpreadsheet` and `SfSpreadsheetRibbon` toolbox items. (If the Syncfusion tab is missing, install the controls using the [Syncfusion® WinForms/WPF installer](https://help.syncfusion.com/wpf/visual-studio-integration/visual-studio-extensions/extensions) and restart Visual Studio.)
-3. Drag `SfSpreadsheetRibbon` and drop in the Designer area from the Toolbox.
+3. Drag `SfSpreadsheet` and `SfSpreadsheetRibbon` from the Toolbox and drop them in the Designer area.
@@ -178,7 +179,7 @@ WPF Spreadsheet control can be added to an application either through the design
{% endhighlight %}
{% endtabs %}
-N> Declare a name for the Spreadsheet component as shown above for reference.
+N> Declare a name for the Spreadsheet component (for example, `x:Name="spreadsheet"`) so that it can be referenced from the Ribbon.
@@ -189,7 +190,7 @@ N> Declare a name for the Spreadsheet component as shown above for reference.
@@ -231,6 +232,10 @@ Spreadsheet is available in the following namespace “_Syncfusion_._UI_._Xaml_.
{% endhighlight %}
{% highlight c# tabtitle="MainWindow.xaml.cs" %}
+using Syncfusion.SfSkinManager;
+using Syncfusion.UI.Xaml.Spreadsheet;
+....
+
public MainWindow()
{
InitializeComponent();
@@ -272,10 +277,15 @@ Press Ctrl+F5 (Windows) or ⌘+F5 (m
-To learn how to create, open, and save files in the WPF Spreadsheet Component, see [Workbook Operations.](Workbook-Operations)
+## Next steps
+
+To learn how to create, open, and save files in the WPF Spreadsheet Component, see [Workbook Operations](Workbook-Operations).
+
+[Find the complete WPF Spreadsheet sample on GitHub.](https://github.com/SyncfusionExamples/create-view-edit-excel-files-using-wpf-spreadsheet)
-N>[View Sample in GitHub.](https://github.com/SyncfusionExamples/create-view-edit-excel-files-using-wpf-spreadsheet). Looking for the full WPF Spreadsheet Editor component overview, features, pricing, and documentation? Visit the [WPF Spreadsheet Editor](https://www.syncfusion.com/spreadsheet-editor-sdk/wpf-spreadsheet-editor) page.
+For the full WPF Spreadsheet Editor component overview, features, pricing, and documentation, visit the [WPF Spreadsheet Editor](https://www.syncfusion.com/spreadsheet-editor-sdk/wpf-spreadsheet-editor) page.
## See Also
+- [Workbook Operations](Workbook-Operations)
- [Data Management](Data-Management)
-- [Display Charts and Sparklines ](Shapes)
\ No newline at end of file
+- [Shapes](Shapes)
\ No newline at end of file
diff --git a/Document-Processing/Excel/Spreadsheet/Winforms/Getting-Started.md b/Document-Processing/Excel/Spreadsheet/Winforms/Getting-Started.md
index 832f5b0aea..fccb03f162 100644
--- a/Document-Processing/Excel/Spreadsheet/Winforms/Getting-Started.md
+++ b/Document-Processing/Excel/Spreadsheet/Winforms/Getting-Started.md
@@ -18,27 +18,29 @@ This section briefly explains how to include the [WinForms Spreadsheet Editor](h
You can create a **Windows Forms Application** using Visual Studio via [Microsoft Templates](https://learn.microsoft.com/en-us/dotnet/desktop/winforms/get-started/create-app-visual-studio) or the [Syncfusion® Windows Forms](https://help.syncfusion.com/windowsforms/visual-studio-integration/template-studio).
-## Assemblies Deployment
+## Installation
-To add a WinForms spreadsheet component to your application by installing it via NuGet packages(Recommended) or by manually adding the required assemblies to the project.
+You can add the WinForms Spreadsheet component to your application either by installing the NuGet package (recommended) or by manually adding the required assemblies to the project.
{% tabcontents %}
-
+
{% tabcontent NuGet Package %}
-### Install Syncfusion® Windows Forms Spreadsheet NuGet packages
+### Install Syncfusion® Windows Forms Spreadsheet NuGet package
-To add **Windows Forms Spreadsheet** component in the application, open the NuGet package manager in Visual Studio (*Tools → NuGet Package Manager → Manage NuGet Packages for Solution*), search and install:
+To add the **Windows Forms Spreadsheet** component in the application, open the NuGet package manager in Visual Studio (*Tools → NuGet Package Manager → Manage NuGet Packages for Solution*), search for and install the following package:
• [Syncfusion.Spreadsheet.Windows](https://www.nuget.org/packages/Syncfusion.Spreadsheet.Windows)
{% endtabcontent %}
-
-{% tabcontent Assemblies (.dll) %}
-### Add Syncfusion® WinForms Spreadsheet Assemblies
+{% tabcontent Manual (.dll) %}
-Below table describes, list of assemblies required to be added in project when the (https://www.syncfusion.com/winforms-ui-controls/spreadsheet) control is used in your application.
+### Add Syncfusion® WinForms Spreadsheet Assemblies
+
+The table below lists the assemblies required to be added to the project when the [Syncfusion WinForms Spreadsheet](https://www.syncfusion.com/winforms-ui-controls/spreadsheet) control is used in your application. The assemblies can be obtained from the Syncfusion Essential Studio installer (default install path: `C:\Program Files (x86)\Syncfusion\Essential Studio\{{site.releaseversion}}\Assemblies`).
+
+**Required Assemblies**
@@ -48,21 +50,22 @@ Description
|
Syncfusion.Spreadsheet.Windows.dll |
-Contains the classes that handles all the UI Operations of Spreadsheet such as importing of sheets, applying formulas/styles etc. |
+Contains the classes that handle all the UI operations of the Spreadsheet, such as importing sheets and applying formulas and styles.
|
Syncfusion.Shared.Base.dll |
-Contains the classes which holds the controls like TabBarPage, TabBarSplitterControl etc. |
+Contains the classes that provide controls like TabBarPage and TabBarSplitterControl.
|
Syncfusion.Tools.Windows.dll |
-Contains the classes which holds the controls like Ribbon, ToolStripPanelItem,MaskedEditBox,ToolStripGallery,BackStageButton etc which are used in Spreadsheet. |
+Contains the classes that provide controls like Ribbon, ToolStripPanelItem, MaskedEditBox, ToolStripGallery, and BackStageButton, which are used in the Spreadsheet.
|
Syncfusion.XlsIO.Base.dll |
-Contains the base classes which is responsible for read and write in Excel files, Worksheet Manipulations, Formula calculations etc. |
+Contains the base classes that are responsible for reading and writing Excel files, worksheet manipulation, and formula calculations.
-Below are the assemblies list that can be added when you want to enable certain features in Spreadsheet control.
+
+The following table lists the optional assemblies that enable additional features in the Spreadsheet control.
@@ -72,47 +75,46 @@ Description
|
Syncfusion.SpreadsheetHelper.Windows.dll |
-Contains the classes which is responsible for importing charts and sparklines into Spreadsheet |
+Contains the classes that import charts and sparklines into the Spreadsheet.
|
Syncfusion.ExcelChartToImageConverter.WPF.dll |
-Contains the classes which is responsible for converting charts as image |
+Contains the classes that convert charts to images.
|
Syncfusion.Chart.Base.dll |
-Contains the base classes which is responsible for importing charts like Line charts, Pie charts, Sparklines etc. |
+Contains the base classes that import charts such as line, pie, and sparklines.
|
Syncfusion.Chart.Windows.dll |
-Contains the classes which is responsible for creating charts that holds axes, series, legends etc. |
+Contains the classes that create charts that hold axes, series, and legends.
|
Syncfusion.ExcelToPDFConverter.Base.dll |
-Contains the base and fundamental classes which is responsible for converting excel to PDF. |
+Contains the base and fundamental classes that convert Excel to PDF.
|
Syncfusion.Pdf.Base.dll |
-Contains the base and fundamental classes for creating PDF. |
+Contains the base and fundamental classes for creating PDFs.
{% endtabcontent %}
{% endtabcontents %}
-## Add Windows Forms Spreadsheet component
+## Add the Windows Forms Spreadsheet Component
-WinForms Spreadsheet control can be added to an application either through the designer (XAML) or programmatically using code.
+WinForms Spreadsheet control can be added to an application either through the designer (Form1.cs[Design]) or programmatically using code.
{% tabcontents %}
-
+
{% tabcontent Via Designer %}
-1. Open the Visual Studio **Tool** **box**. Navigate to Syncfusion® Controls tab and find the Spreadsheet/SpreadsheetRibbon toolbox items.
+1. Open the Visual Studio **Toolbox**. Navigate to the **Syncfusion® Controls** tab and find the `Spreadsheet` and `SpreadsheetRibbon` toolbox items.
-2. Drag `Spreadsheet` and drop in the Designer area from the Toolbox.
-
+2. Drag `Spreadsheet` and `SpreadsheetRibbon` from the Toolbox onto the Designer area.
{% tabs %}
{% highlight c# tabtitle="Form1.Designer.cs" %}
....
@@ -172,14 +174,14 @@ spreadsheetRibbon.Spreadsheet = spreadsheet;
{% tabcontent Via Coding %}
-
-Spreadsheet is available in the following namespace **[Syncfusion.Windows.Forms.Spreadsheet](https://help.syncfusion.com/cr/windowsforms/Syncfusion.Windows.Forms.Spreadsheet.html)** and it can be created programmatically by using below code.
+The `Spreadsheet` control is available in the [Syncfusion.Windows.Forms.Spreadsheet](https://help.syncfusion.com/cr/windowsforms/Syncfusion.Windows.Forms.Spreadsheet.html) namespace and can be created programmatically with the following code.
_For_ _Spreadsheet_
{% tabs %}
{% highlight c# tabtitle="Form1.cs" %}
+using Syncfusion.Windows.Forms.Spreadsheet;
....
public Form1()
{
@@ -196,21 +198,24 @@ _For_ _Spreadsheet_
{% endhighlight %}
{% endtabs %}
-
{% endtabcontent %}
{% endtabcontents %}
-## Run the application
+## Run the Application
-Press Ctrl+F5 (Windows) or ⌘+F5 (macOS) to launch the application.The output will appear as follows:
+Press Ctrl+F5 (Windows) or ⌘+F5 (macOS) in Visual Studio to launch the application.The output will appear as follows:
-To learn how to create, open, and save files in the WPF Spreadsheet Component, see [Workbook Operations](Workbook-Operations).
+## Next Steps
-N>[View Sample in GitHub.](https://github.com/SyncfusionExamples/winforms-spreadsheet-getting-started). Looking for the full Winforms Spreadsheet Editor component overview, features, pricing, and documentation? Visit the [Winforms Spreadsheet Editor](https://www.syncfusion.com/spreadsheet-editor-sdk/winforms-spreadsheet-editor) page.
+* To learn how to create, open, and save files in the WinForms Spreadsheet control, see [Workbook Operations](Workbook-Operations).
+* For a complete working sample that demonstrates everything in this getting-started guide, see the [WinForms Spreadsheet Getting Started sample on GitHub](https://github.com/SyncfusionExamples/winforms-spreadsheet-getting-started).
+* For a full overview of the WinForms Spreadsheet Editor component, including features, pricing, and documentation, visit the [WinForms Spreadsheet Editor](https://www.syncfusion.com/spreadsheet-editor-sdk/winforms-spreadsheet-editor) page.
## See Also
-- [Data Management](Data-Management)
-- [Display Charts and Sparklines](Shapes)
+* [Data Management](Data-Management)
+* [Formatting](Formatting)
+* [Formulas](Formulas)
+* [Display Charts and Sparklines](Shapes)
diff --git a/Document-Processing/Licensing/how-to-generate.md b/Document-Processing/Licensing/how-to-generate.md
index 3ed184b9af..c7ac4764d9 100644
--- a/Document-Processing/Licensing/how-to-generate.md
+++ b/Document-Processing/Licensing/how-to-generate.md
@@ -13,8 +13,15 @@ License keys for Document Processing can be generated from the [License & Downlo
-I> * Syncfusion® license keys are **version and platform specific**, refer to the [KB](https://www.syncfusion.com/kb/8976/how-to-generate-license-key-for-licensed-products) to generate the license key for the required version and platform.
-* Refer this [KB](https://www.syncfusion.com/kb/8951/which-version-syncfusion-license-key-should-i-use-in-my-application) to know about which version of the Syncfusion® license key should be used in the application.
+I> * Syncfusion® license keys are **version‑specific and edition‑specific**, refer to the [KB](https://www.syncfusion.com/kb/8976/how-to-generate-license-key-for-licensed-products) to generate the license key for the required version and platform.
+* **Starting from v31.1.17 (2025 Volume 3 release)**, Syncfusion® introduced a new licensing model where license keys are generated **per edition rather than per platform.** The editions include:
+ - **Essential Studio UI Edition**
+ - **Essential Studio Document SDK**
+ - **Essential Studio PDF Viewer SDK**
+ - **Essential Studio DOCX Editor SDK**
+ - **Essential Studio Spreadsheet Editor SDK**
+ - **Essential Studio Enterprise Edition** (includes all the above)
+* **Previously (before v31.x)**, Syncfusion® generated license keys **per platform** (e.g., File Formats).
## Claim License key
diff --git a/Document-Processing/Licensing/licensing-faq/CI-license-validation.md b/Document-Processing/Licensing/licensing-faq/CI-license-validation.md
index f393b77a33..681f0cd751 100644
--- a/Document-Processing/Licensing/licensing-faq/CI-license-validation.md
+++ b/Document-Processing/Licensing/licensing-faq/CI-license-validation.md
@@ -1,7 +1,7 @@
---
layout: post
title: Overview of Syncfusion license validation in CI services - Syncfusion
-description: Learn here about how to register Syncfusion license key for Syncfusion application for license validation.
+description: Learn how to register and validate the Syncfusion license key for your application in CI services.
platform: file-formats
control: Essential Studio
documentation: ug
@@ -17,18 +17,35 @@ margin-top: 1.5em; margin-bottom: 1.5em;
-# Syncfusion® license key validation in CI services
+# Overview of Syncfusion license validation in CI services
-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.
+Validating the Syncfusion® license key as part of your CI pipeline ensures that Syncfusion® Essential Studio components are properly licensed before deployment and helps prevent licensing errors in production. The following sections describe how to validate the license key in Azure Pipelines, GitHub Actions, and Jenkins, and how to validate it programmatically using the `ValidateLicense()` method or a unit test project.
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](https://s3.amazonaws.com/files2.syncfusion.com/Installs/LicenseKeyValidation/LicenseKeyValidator.zip).
-* Open the LicenseKeyValidation.ps1 PowerShell script in a text\code editor as shown in the below example.
+* Open the LicenseKeyValidation.ps1 PowerShell script in a text or code editor as shown in the following example.
+
{% tabs %}
-{% highlight c# tabtitle="PowerShell" %}
+{% highlight c# tabtitle="v34.1.29 and later" %}
+# Replace the parameters with the desired platform, version, and actual license key.
+
+$result = & $PSScriptRoot"\LicenseKeyValidatorConsole.exe" /platform:"WordToPDF" /version:"34.1.29" /licensekey:"Your License Key"
+
+Write-Host $result
+{% endhighlight %}
+
+{% highlight c# tabtitle="v31.1.17 to v33.2.3" %}
+# Replace the parameters with the desired platform, version, and actual license key.
+
+$result = & $PSScriptRoot"\LicenseKeyValidatorConsole.exe" /platform:"WordToPDF" /version:"31.1.17" /licensekey:"Your License Key"
+
+Write-Host $result
+{% endhighlight %}
+
+{% highlight c# tabtitle="Before v31.1.17" %}
# Replace the parameters with the desired platform, version, and actual license key.
$result = & $PSScriptRoot"\LicenseKeyValidatorConsole.exe" /platform:"FileFormats" /version:"26.2.4" /licensekey:"Your License Key"
@@ -37,28 +54,28 @@ Write-Host $result
{% endhighlight %}
{% endtabs %}
-
+* Update the parameters in the script:
+
+ **Platform:** Set /platform:"**WordToPDF**" for v34.1.29 and later and v31.1.17 to v33.2.3, or /platform:"**FileFormats**" for before v31.1.17 (use the relevant Syncfusion platform as needed).
-* Update the parameters in the LicenseKeyValidation.ps1 script file as described below.
+ **Version:** Change the value for `/version:` to the required version (for example, `26.2.4`).
- **Platform:** Modify the value for /platform: to the actual platform "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").
-
- N> This feature is supported only from the 16.2.0.41 version of the Essential Studio®.
+ **License Key:** Replace the value for `/licensekey:` with your actual license key (for example, `Your License Key`). To keep the key out of source control, store it as a CI secret and read it in the script (for example, `$env:SYNCFUSION_LICENSE_KEY`).
+
+ N> This feature is supported starting with version 16.2.0.41 of Essential Studio®.
+
+ N> On Windows agents, if script execution is blocked by policy, run the script with `-ExecutionPolicy Bypass` (for example, `powershell -ExecutionPolicy Bypass -File .\LicenseKeyValidation.ps1`). The script returns a non-zero exit code when validation fails so the pipeline step fails.
## 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 the 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 the value (for example, `D:\LicenseKeyValidator\LicenseKeyValidation.ps1`).
-* Integrate the PowerShell task in the 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 yaml tabtitle="YAML" %}
pool:
vmImage: 'windows-latest'
@@ -75,21 +92,21 @@ 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 the 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 the value (for example, `D:\LicenseKeyValidator\LicenseKeyValidation.ps1`). Store the license key as a secret variable (for example, `SYNCFUSION_LICENSE_KEY`).
-* Include the PowerShell task in the pipeline and execute the script to validate the license key.
+* Add a PowerShell task that runs the script. Mark the build to fail when the script's exit code is non-zero so the pipeline reflects validation failures.
-## GitHub actions
+## 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).
+* To execute the script in PowerShell as part of a GitHub Actions workflow, add a step in the workflow YAML file. Update the path of the LicenseKeyValidation.ps1 script file (for example, `./path/LicenseKeyValidator/LicenseKeyValidation.ps1`) and store the license key in a repository or organization secret named `SYNCFUSION_LICENSE_KEY`.
-The following example shows the syntax for validating the 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" %}
- steps:
+{% highlight yaml tabtitle="YAML" %}
+steps:
- name: Syncfusion License Validation
shell: pwsh
run: |
@@ -99,9 +116,9 @@ The following example shows the syntax for validating the Syncfusion®® license key in the Jenkins pipeline.
@@ -125,41 +142,64 @@ pipeline {
## Validate the License Key By Using the ValidateLicense() Method
-* Register the license key properly by calling RegisterLicense("License Key") method with the license key.
+* Register the license key by calling `SyncfusionLicenseProvider.RegisterLicense("YOUR LICENSE KEY")` before any Syncfusion control is instantiated.
-* Once the license key is registered, it can be validated by using the ValidateLicense("Platform.FileFormats") method. This ensures that the license key is valid for the platform and version you are using. For reference, please check the following example.
+* After registration, validate the key with `SyncfusionLicenseProvider.ValidateLicense(Platform.FileFormats)`, passing the `Platform` enum value that matches your application. This confirms the license is valid for the platform and version in use. The method returns `true` on success and `false` on failure; in overloads that include an `out string validationMessage` parameter, the message describes the failure reason. See the following examples for the correct signature by version.
{% tabs %}
-{% highlight c# %}
+{% highlight csharp tabtitle="v34.1.29 and later" %}
+using Syncfusion.Licensing;
+
+// Register the Syncfusion license key
+SyncfusionLicenseProvider.RegisterLicense("YOUR LICENSE KEY");
+
+// Validate the registered license key.
+// The array overload allows validating against multiple platforms in a single call.
+bool isValid = SyncfusionLicenseProvider.ValidateLicense(new[] { Platform.WordToPDF });
+{% endhighlight %}
+
+{% highlight csharp tabtitle="v31.1.17 to v33.2.3" %}
+using Syncfusion.Licensing;
+
+// Register the Syncfusion license key
+SyncfusionLicenseProvider.RegisterLicense("YOUR LICENSE KEY");
+
+// Validate the registered license key
+bool isValid = SyncfusionLicenseProvider.ValidateLicense(Platform.WordToPDF);
+{% endhighlight %}
+
+{% highlight csharp tabtitle="Before v31.1.17" %}
using Syncfusion.Licensing;
-//Register Syncfusion license key
-Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense("YOUR LICENSE KEY");
+// Register the Syncfusion license key
+SyncfusionLicenseProvider.RegisterLicense("YOUR LICENSE KEY");
-//Validate the registered license key
+// Validate the registered license key
bool isValid = SyncfusionLicenseProvider.ValidateLicense(Platform.FileFormats);
{% endhighlight %}
{% endtabs %}
-
+N> Use the specific platform enum (`PDF`, `Word`, `Excel`, `PowerPoint`, `WordToPDF`, `ExcelToPDF`, or `PowerPointToPDF`) for license validation from v31.1.17 and later. `Platform.FileFormats` is not supported from v31.1.17 onwards.
+
+* If the `ValidateLicense()` method returns `true`, the registered license key is valid and the build can proceed with deployment.
-* If the ValidateLicense() method returns true, registered license key is valid and can proceed with deployment.
+* If the `ValidateLicense()` method returns `false`, the build produces invalid license errors. Validation fails when the license key is invalid or the referenced Syncfusion assembly or package versions do not match the version of the license key. Ensure that all referenced Syncfusion® assemblies or NuGet packages share the same version as the license key 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.
+## Validate the License Key By Using the Unit Test Project
-## 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. Filter the project type by Test, or type **Test** as a keyword in the search option, to find available unit test projects. Select the appropriate test framework (such as MSTest, NUnit, or xUnit) that best suits your need.
-* 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.
+* Add the required Syncfusion references to the test project. The example below uses NUnit, so install the NUnit and NUnit3TestAdapter NuGet packages, then add the `Syncfusion.Licensing` package and the File-Formats platform package (for example, `Syncfusion.PdfToPdfAConverter` or the platform package relevant to your project) at the same version as your license key.
* For more details on creating unit test projects in Visual Studio, refer to the [Getting Started with Unit Testing guide](https://learn.microsoft.com/en-us/visualstudio/test/getting-started-with-unit-testing?view=vs-2022&tabs=dotnet%2Cmstest#create-unit-tests).
-* Register the license key by calling the RegisterLicense("Your License Key") method with the license key in the unit test project.
+* Register the license key by calling `SyncfusionLicenseProvider.RegisterLicense("Your License Key")` in the unit test project. Register the key before any Syncfusion control is instantiated so the validation reflects the runtime configuration.
-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.
+N> Enclose the license key in double quotes. Also, ensure that `Syncfusion.Licensing` (the `Syncfusion.Licensing.dll` assembly) is referenced in the project where the license key is registered. For .NET Core/5+ projects, add the `Syncfusion.Licensing` NuGet package; for .NET Framework projects, reference `Syncfusion.Licensing.dll` from the installed Essential Studio assemblies.
-* Once the license key is registered, it can be validated by using the ValidateLicense("Platform.FileFormats", out var validationMessage) method. This ensures that the license key is valid for the platform and version you are using.
+* Once the license key is registered, it can be validated by using the `ValidateLicense(Platform.FileFormats, out string validationMessage)` method. The `validationMessage` out parameter describes the failure reason when the result is `false`, which makes troubleshooting easier in unit-test output.
* For reference, please check the following example that demonstrates how to register and validate the license key in the unit test project.
@@ -183,12 +223,12 @@ public void TestSyncfusionFileFormatsLicense()
{% endhighlight %}
{% endtabs %}
-* 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.
+* Once the unit test is executed, if the license key validation passes for the specified platform, output similar to the following is displayed in the **Test Explorer** window.
-* If the license validation fails during unit testing, the following output will be displayed in the Test Explorer window.
+* If the license validation fails during unit testing, output similar to the following is displayed in the **Test Explorer** window.
-* 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.
\ No newline at end of file
+* Validation fails when the license key is invalid or the referenced Syncfusion assembly or package versions do not match the version of the license key. Verify that you are using a valid key for the platform and that all referenced Syncfusion packages share the same version as the license key.
\ No newline at end of file
diff --git a/Document-Processing/PDF/Conversions/PDF-to-image/NET/Assemblies-Required.md b/Document-Processing/PDF/Conversions/PDF-to-image/NET/Assemblies-Required.md
index 653f7bd449..6e7e01642c 100644
--- a/Document-Processing/PDF/Conversions/PDF-to-image/NET/Assemblies-Required.md
+++ b/Document-Processing/PDF/Conversions/PDF-to-image/NET/Assemblies-Required.md
@@ -8,7 +8,7 @@ documentation: UG
# Assemblies Required to work with PDFToImageConverter
-TThe following assemblies need to be referenced in your application based on the platform.
+The following assemblies need to be referenced in your application based on the target platform.
@@ -26,8 +26,7 @@ Syncfusion.PdfToImageConverter.Base
-
-| Blazor, .NET Core and .NET Platforms |
+Blazor, .NET Core, and .NET Platforms |
Syncfusion.PdfToImageConverter.Portable
SkiaSharp
@@ -41,5 +40,4 @@ SkiaSharp
Syncfusion.SkiaSharpHelper.NET
|
-
-
+ |