diff --git a/Extension/ASPNET-Extension/Check-for-Updates.md b/Extension/ASPNET-Extension/Check-for-Updates.md
index 656aacd9..9a3bb44f 100644
--- a/Extension/ASPNET-Extension/Check-for-Updates.md
+++ b/Extension/ASPNET-Extension/Check-for-Updates.md
@@ -17,12 +17,12 @@ You can check the availability of updates in Visual Studio and then install the
1. Choose **Syncfusion® -> Check for Updates…** in the Visual Studio menu
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
2. When an update is available, the Update dialog box appears.
- 
+ 
3. Syncfusion® Essential Studio® can be downloaded from the Syncfusion® website by clicking the **Download** button.
diff --git a/Extension/ASPNET-Extension/Overview.md b/Extension/ASPNET-Extension/Overview.md
index 31f8ef79..9f65f72d 100644
--- a/Extension/ASPNET-Extension/Overview.md
+++ b/Extension/ASPNET-Extension/Overview.md
@@ -26,15 +26,15 @@ The Syncfusion® provides the following exte
**No project selected in Visual Studio**
-
+
**Selected Microsoft ASP.NET WebSite or Web application in Visual Studio**
-
+
**Selected Syncfusion® ASP.NET (Essential® JS1) WebSite or Web application in Visual Studio**
-
+
N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
diff --git a/Extension/ASPNET-Extension/Project-Conversion.md b/Extension/ASPNET-Extension/Project-Conversion.md
index 44d52418..6044fec1 100644
--- a/Extension/ASPNET-Extension/Project-Conversion.md
+++ b/Extension/ASPNET-Extension/Project-Conversion.md
@@ -24,18 +24,18 @@ The following steps will assist you to use the Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Convert to Syncfusion® ASP.NET Application…** in **Visual Studio**.
- 
+ 
N> In Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
**Option 2**
Right-click the Project from Solution Explorer, select **Syncfusion® Web (Essential® JS 1)**, and choose the **Convert to Syncfusion® ASP.NET (Essential® JS 1) Application...** Refer to the following screenshot for more information.
- 
+ 
3. The Project Conversion Wizard appears, allowing you to configure the project.
- 
+ 
The following configurations are used in the Project Conversion wizard:
@@ -49,7 +49,7 @@ The following steps will assist you to use the Syncfusion® CDN links.
- 
+ 
**Copy Global Resources:** If you select the Copy Global Resources option, the Syncfusion® localization culture files will be shipped to the project from the Installed Location.
@@ -63,14 +63,14 @@ The following steps will assist you to use the Syncfusion® project. If you choose **No**, the project will be converted to a Syncfusion® project without a backup.
- 
+ 
5. The necessary Syncfusion® Assembly references, Scripts, and CSS, as well as the necessary Web.config entries, have been added to the project.
- 
+ 
- 
+ 
- 
+ 
6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®.
\ No newline at end of file
diff --git a/Extension/ASPNET-Extension/Project-Migration.md b/Extension/ASPNET-Extension/Project-Migration.md
index 0460ccb1..9569328a 100644
--- a/Extension/ASPNET-Extension/Project-Migration.md
+++ b/Extension/ASPNET-Extension/Project-Migration.md
@@ -22,18 +22,18 @@ To migrate you’re existing Syncfusion® AS
**Option 1**
Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Migrate Project…** in **Visual Studio**.
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
**Option 2**
Right-click the **Syncfusion® ASP.NET Application** from Solution Explorer and select **Syncfusion® Web (Essential® JS 1)**. Choose **Migrate the Essential® JS 1 Project to Another version…**
- 
+ 
2. The **Project Migration** window appears. You can choose the required Essential Studio® version that is installed in the machine.
- 
+ 
3. The **Project Migration** window allows you to configure the following options:
@@ -45,7 +45,7 @@ To migrate you’re existing Syncfusion® AS
4. Click the **Migrate** Button. The **Project Backup** dialogue box appears. If you select **Yes** in the dialog, it will backup the current project before migrating the Syncfusion® project. If you select **No**, the project will be migrated to the required Syncfusion® version without a backup.
- 
+ 
5. The Syncfusion® Reference Assemblies, Scripts, and CSS, Web. Config entries in the project are updated to the corresponding version.
diff --git a/Extension/ASPNET-Extension/Sample-Creator.md b/Extension/ASPNET-Extension/Sample-Creator.md
index 3e71a8cb..3bc7f464 100644
--- a/Extension/ASPNET-Extension/Sample-Creator.md
+++ b/Extension/ASPNET-Extension/Sample-Creator.md
@@ -18,26 +18,26 @@ To create the Syncfusion® ASP.NET (Essentia
**Option 1:**
Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Launch Sample Creator…** in **Visual Studio**.
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
**Option 2:**
Launch the Syncfusion® ASP.NET (Essential® JS 1) Control Panel. To run the ASP.NET (Essential® JS 1) Sample Creator, click the Sample Creator button. More information can be found in the screenshot below.
- 
+ 
2. The Syncfusion® components and their features are listed in the ASP.NET (Essential® JS 1) Sample Creator.
- 
+ 
**Components Selection:** Choose the required components. The components are grouped with Syncfusion® products, and the components are grouped by product.
- 
+ 
**Feature Selection:** Based on the components, the feature is enabled to choose the features of the corresponding components.
- 
+ 
**Project Configuration**
@@ -55,29 +55,29 @@ To create the Syncfusion® ASP.NET (Essentia
* **Theme Selection:** Choose the required theme. This section shows the controls preview before creating the Syncfusion® project.
- 
+ 
2. Click the **Create** button. After you've finished creating the project, open it by clicking **Yes**. If you click **No**, the project's corresponding location will be opened. For more information, see the screenshot below.
- 
+ 
3. The new Syncfusion® ASP.NET (Essential® JS 1) project is created with the resources.
* Added the required Controllers and View files in the project.
- 
+ 
* Under Project Reference, the necessary Syncfusion® assemblies are added for selected components.
- 
+ 
* Syncfusion® ASP.NET (Essential® JS 1) scripts and theme files were included.
- 
+ 
* Configure the Web.Config file by adding the Syncfusion® reference assemblies, namespaces and controls.
- 
+ 
diff --git a/Extension/ASPNET-Extension/Syncfusion-Project-Templates.md b/Extension/ASPNET-Extension/Syncfusion-Project-Templates.md
index 236b0557..12a2d3ad 100644
--- a/Extension/ASPNET-Extension/Syncfusion-Project-Templates.md
+++ b/Extension/ASPNET-Extension/Syncfusion-Project-Templates.md
@@ -22,14 +22,14 @@ To create the **Syncfusion® ASP.NET (Essent
**Option 1**
Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Create New Syncfusion® ASPNET Web Forms Project…** in **Visual Studio**.
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
**Option 2**
Choose **File > New > Project** and navigate to **Syncfusion > Web > Syncfusion® ASP.NET Web Forms Application** in **Visual Studio**.
- 
+ 
2. Name the **project**, select the destination location, and configure the project's .NET Framework, then click **OK**. The Project Configuration Wizard is displayed.
@@ -37,7 +37,7 @@ To create the **Syncfusion® ASP.NET (Essent
3. Using the following Project Configuration window, select the options to configure the Syncfusion® ASP.NET Web Forms Application.
- 
+ 
**Project Configurations**
@@ -59,7 +59,7 @@ To create the **Syncfusion® ASP.NET (Essent
**Assets From:** Choose the Syncfusion® Essential® JS assets to be added to the ASP.NET Web Forms Project from the NuGet, CDN, or Installed Location.
- 
+ 
**Installed Version** Choose the version of the project that needs to be created.
@@ -67,22 +67,22 @@ To create the **Syncfusion® ASP.NET (Essent
4. Select the components, Assemblies, and Scripts that should be added to the project, and then click the Create button. The Syncfusion® ASP.NET Web Forms project will be created.
- 
+ 
- 
+ 
5. The necessary Syncfusion® Assembly references, Scripts, and CSS, as well as the necessary Web.config entries, have been added to the project.
- 
+ 
- 
+ 
- 
+ 
6.Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
+ 
diff --git a/Extension/ASPNET-Extension/Toolbox-Configuration.md b/Extension/ASPNET-Extension/Toolbox-Configuration.md
index c9c1187a..03f25100 100644
--- a/Extension/ASPNET-Extension/Toolbox-Configuration.md
+++ b/Extension/ASPNET-Extension/Toolbox-Configuration.md
@@ -27,7 +27,7 @@ To add the Syncfusion® ASP.NET Web Forms co
**Option 2:**
Click **Syncfusion® menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Toolbox Configuration...** in **Visual Studio**
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
diff --git a/Extension/ASPNET-Extension/Troubleshooting.md b/Extension/ASPNET-Extension/Troubleshooting.md
index 28708c1f..3f156345 100644
--- a/Extension/ASPNET-Extension/Troubleshooting.md
+++ b/Extension/ASPNET-Extension/Troubleshooting.md
@@ -26,14 +26,14 @@ The steps below will assist you in using the Syncfusion® ASP.NET Web Forms Application, Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Troubleshoot…** in Visual Studio.
- 
+ 
N> In Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
**Option 2**
Right-click the Project file in Solution Explorer, then select the command **Syncfusion® Troubleshooter…**
- 
+ 
2. Now, analyze the project, and if any issues are discovered, it will report the project configuration issues of Syncfusion® components in the Troubleshooter dialogue. If the project has no configuration issues, the dialogue box will indicate that no configuration changes are required in the following areas:
@@ -97,7 +97,7 @@ The Syncfusion® Troubleshooter handles the
**For Instance:** If you have multiple versions of the Syncfusion® Web platform packages installed (v16.4.0.54 and v17.1.0.38), the Syncfusion® Troubleshooter will display Syncfusion® package version mismatch.
- 
+ 
2. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing.
@@ -115,17 +115,17 @@ The Syncfusion® Troubleshooter handles with
**For Instance:** If the “Syncfusion.EJ.Pivot” assembly (v17.1450.0.38) is mentioned in the project, but the “Syncfusion.EJ.Pivot” assembly entry version (v16.4450.0.54) is mentioned in the Web.config file. The Syncfusion® Troubleshooter will display a mismatched Syncfusion® assembly entry version.
- 
+ 
2. Syncfusion® assembly entry has multiple versions and is duplicated. When a Syncfusion® assembly entry is presented in Web.config that is not referred to in the project, or when multiple Syncfusion® assembly entries are presented in Web.config for the same Syncfusion® assembly, Syncfusion® Troubleshooter will display the duplicate assembly entry.
**For Instance:** If the project contains a “Syncfusion.EJ.Web” assembly (v17.1450.0.38) entry in the Web.config file, but the “Syncfusion.EJ.Web” assembly is not referred to in the project. Duplicate assembly entry will be displayed by Syncfusion® Troubleshooter.
- 
+ 
**For Instance:** If a project contains multiple “Syncfusion.EJ.Web” assembly entries (v16.4460.0.54 && v17.1460.0.38) with mismatched assembly version/.NET Framework version in Web.config, Syncfusion® Troubleshooter will display the Duplicate assembly entry and Multiple Syncfusion® assembly entries.
- 
+ 
3. The version of the namespace entry was mismatched. If any Namespace entry version (assembly version) in ASP.NET Web Application is mismatched with the corresponding referred assembly version, Syncfusion® Troubleshooter will display Namespace entry version mismatched.
@@ -137,7 +137,7 @@ The Syncfusion® Troubleshooter handles with
**For Instance:** If the “Syncfusion.EJ.” assembly (v17.1450.0.38) is mentioned in the project, but the “Syncfusion.JavaScript.ImageHandler” HTTP/Server handler entry version (v16.4450.0.54) is specified in the Web.config file. The Syncfusion® Troubleshooter will display a mismatched Syncfusion® HTTP/Server handler entry version.
- 
+ 
### Toolbox Configuration Issues
@@ -147,13 +147,13 @@ The Syncfusion® Troubleshooter handles the
**For Instance:** The .NET Framework version of the project is 4.5, and Syncfusion® Toolbox is not installed. 4.6 framework assemblies only in the corresponding Visual Studio, the Syncfusion® Troubleshooter will display Syncfusion® Toolbox framework version mismatch.
- 
+ 
2. If the configured version of Syncfusion® Toolbox differs from the most recent Syncfusion® assembly reference version or NuGet package version in the same project, the Syncfusion® Troubleshooter will indicate that the Syncfusion® Toolbox version is mismatch.
**For Instance:** If the most recent Syncfusion® assembly reference version is v17.1.0.38 but the Toolbox assemblies are configured with v17.1.0.32, the Syncfusion Troubleshooter will report Syncfusion® Toolbox version mismatch.
- 
+ 
### Script file issues
@@ -163,36 +163,36 @@ The Syncfusion® Troubleshooter handles the
**For Instance:** If Syncfusion® assemblies (v17.1450.0.38) and Syncfusion® script file (v16.4.0.54) are referenced in the project. The Syncfusion® Troubleshooter will display a Syncfusion® script file version (v16.4.0.54) that is incompatible with the project's/package version of Syncfusion® (v17.1.0.38).
- 
+ 
**For Instance:** If Syncfusion® assemblies (v17.1450.0.38) are referred to in the project, but Syncfusion® script file version (v16.4.0.54) is referred to in View files when script files are referred to via a CDN link. The Syncfusion® Troubleshooter will report that the Syncfusion® script file version (v16.4.0.54) is incompatible with the project's Syncfusion® assembly/package version (v17.1.0.38) from CDN.
- 
+ 
2. Syncfusion® script files that are duplicates. When a Syncfusion® script file is presented in the project location, which is referred to in View files by CDN link, or when Syncfusion® script files are presented in multiple locations in the same project, Syncfusion® Troubleshooter will display duplicate script files.
**For Instance:** If the project has a “ej.web.all.min.js” script file entry in the View file and a “ej.web.all.min.js” script file in the project location (Scripts\ej), the Syncfusion® Troubleshooter will show duplicate Syncfusion® script files presented in Scripts\ej due to this script file being referred from CDN.
- 
+ 
**For Instance:** If a project has the “ej.web.all.min.js” script file available in multiple project locations ("\Scripts\ej" and "\Scripts\"), the Syncfusion® Troubleshooter will display Duplicate Syncfusion® script files in Scripts.
- 
+ 
## Apply the solution
1. Check the corresponding check box of the issue to be resolved after loading the Syncfusion® Troubleshooter dialog. Then, check “Fix Issue(s)” button.
- 
+ 
2. A dialog appears, prompting you to create a backup of the project before proceeding with the troubleshooting process. Click the "Yes" button if you need to backup the project before troubleshooting.
- 
+ 
3. Wait a moment while the Syncfusion® Troubleshooter resolves the issues you selected. When the troubleshooting process is finished, a message will appear in the Visual Studio status bar that says, "Troubleshooting process completed successfully."
- 
+ 
4. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/Extension/ASPNET-MVC-Extension/Command-Line-installation.md b/Extension/ASPNET-MVC-Extension/Command-Line-installation.md
index c1aa1cd5..a7abad14 100644
--- a/Extension/ASPNET-MVC-Extension/Command-Line-installation.md
+++ b/Extension/ASPNET-MVC-Extension/Command-Line-installation.md
@@ -24,6 +24,6 @@ The following steps help you install the Syncfusion&r
Refer to the following screenshot for more information.
- 
+ 
I> The syncfusionessentialextension.exe setup has renamed to syncfusionwebsamplecreator.exe from 2015 Volume 4 release.
\ No newline at end of file
diff --git a/Extension/ASPNET-MVC-Extension/Download-ASPNET-MVC-Extension.md b/Extension/ASPNET-MVC-Extension/Download-ASPNET-MVC-Extension.md
index 6da0ef08..9249e5c3 100644
--- a/Extension/ASPNET-MVC-Extension/Download-ASPNET-MVC-Extension.md
+++ b/Extension/ASPNET-MVC-Extension/Download-ASPNET-MVC-Extension.md
@@ -13,7 +13,7 @@ documentation: ug
Refer the following screenshot for more information.
- 
+ 
I> It is a prerequisite to have the complete Essential Studio® suite or ASP.NET MVC or ASP.NET MVC (Classic) installed while using Syncfusion® ASP.NET MVC Extension. This is applicable from v.12.1.0.43.
@@ -23,7 +23,7 @@ documentation: ug
* Navigate to the “ASP.NET MVC” tab available on the left side.
* Click the “SAMPLE CREATOR” button. It downloads the corresponding version of Syncfusion® Web Sample Creator setup. When you have already installed the Syncfusion® Web Sample Creator setup then it will launch the “Sample Creator” utility instead of downloading.
- 
+ 
I> The syncfusionessentialextension.exe setup has renamed to syncfusionwebsamplecreator.exe from 2015 Volume 4 release.
diff --git a/Extension/ASPNET-MVC-Extension/Overview.md b/Extension/ASPNET-MVC-Extension/Overview.md
index bab3708b..21f90c77 100644
--- a/Extension/ASPNET-MVC-Extension/Overview.md
+++ b/Extension/ASPNET-MVC-Extension/Overview.md
@@ -23,15 +23,15 @@ The Syncfusion® provides the following exte
**No project selected in Visual Studio**
-
+
**Selected Microsoft ASP.NET MVC application in Visual Studio**
-
+
**Selected Syncfusion® ASP.NET MVC (Essential® JS1) application in Visual Studio**
-
+
N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
diff --git a/Extension/ASPNET-MVC-Extension/Project-Conversion.md b/Extension/ASPNET-MVC-Extension/Project-Conversion.md
index 669a125d..064fe32a 100644
--- a/Extension/ASPNET-MVC-Extension/Project-Conversion.md
+++ b/Extension/ASPNET-MVC-Extension/Project-Conversion.md
@@ -42,18 +42,18 @@ The following steps help you use the Syncfusion®<
**Option 1:**
Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ1) > Convert to Syncfusion® ASP.NET MVC Application…** in **Visual Studio**.
- 
+ 
N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
**Option 2:**
Right-click the Project from Solution Explorer, select **Syncfusion® Essential® JS 1**, and choose **Convert to Syncfusion® MVC (Essential® JS 1) Application...** Refer to the following screenshot for more information.
- 
+ 
3. Project Conversion Wizard opens so that you can configure the project.
- 
+ 
The following configurations are used in the Project Conversion Wizard.
@@ -77,7 +77,7 @@ The following steps help you use the Syncfusion®<
The master page of the project will be updated based on required Syncfusion® CDN links.
- 
+ 
**Choose Copy Global Resources:**
@@ -87,20 +87,20 @@ The following steps help you use the Syncfusion®<
4. Choose the required controls from Components section and Click the **Convert** button to convert it into a Syncfusion Project.
- 
+ 
5. The **Project Backup** dialog will be opened. If click Yes it will backup the current project before converting it to Syncfusion® project. If click No it will convert the project to Syncfusion® project without backup.
- 
+ 
6. The required Syncfusion® Reference Assemblies, Scripts and CSS are included in the MVC Project. Refer to the following screenshots for more information.
- 
+ 
- 
+ 
- 
+ 
6. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®.
@@ -112,11 +112,11 @@ The following steps help you use the Syncfusion®<
2. Right-click on Project and select Syncfusion® VS Extensions and choose the Convert to Syncfusion® MVC (Web) Application. Refer the following screenshot for more information.
- 
+ 
3. Project Conversion Wizard opens so that you can configure the project.
- 
+ 
The following configurations are used in the Project Conversion Wizard.
@@ -140,7 +140,7 @@ The following steps help you use the Syncfusion®<
The master page of the project will be updated based on required Syncfusion® CDN links.
- 
+ 
**Choose Copy Global Resources:**
@@ -152,13 +152,13 @@ The following steps help you use the Syncfusion®<
5. The required Syncfusion® Reference Assemblies, Scripts and CSS are included in the MVC Project. Refer to the following screenshots for more information.
- 
+ 
- 
+ 
- 
+ 
- 
+ 
## Rendering Control after Syncfusion® MVC (Web/Mobile) Conversion:
@@ -171,9 +171,9 @@ Once you convert your ASP.NET MVC project to Syncfusion® controls to your project. Refer to the following screenshot for more information.
- 
+ 
4. Run the project and the following output is displayed.
- 
+ 
diff --git a/Extension/ASPNET-MVC-Extension/Project-Migration.md b/Extension/ASPNET-MVC-Extension/Project-Migration.md
index 18d4fbcd..a2dd1d3d 100644
--- a/Extension/ASPNET-MVC-Extension/Project-Migration.md
+++ b/Extension/ASPNET-MVC-Extension/Project-Migration.md
@@ -11,7 +11,7 @@ documentation: ug
Project Migration is a Visual Studio add-in that helps migrate the existing Syncfusion® ASP.NET MVC (Web), Syncfusion® ASP.NET MVC (Mobile) Or Syncfusion® ASP.NET MVC (Classic) project from one Syncfusion® version to another Syncfusion® version.
-Syncfusion® ASP.NET MVC and ASP.NET MVC (Classic) Project Migration Utility is included here,
+Syncfusion ASP.NET MVC and ASP.NET MVC (Classic) Project Migration Utility is included here,
* Essential Studio® for Enterprise Edition with the platforms ASP.NET MVC or ASP.NET MVC(Classic)
* Essential Studio® for ASP.NET MVC
@@ -40,18 +40,18 @@ The following steps help you migrate from one version to another version of your
**Option 1:**
Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ1) > Migrate Project…** in **Visual Studio**.
- 
+ 
N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
**Option 2:**
Right-click the **Syncfusion® ASP.NET MVC Application** from Solution Explorer and select **Syncfusion® Essential® JS 1**. Choose **Migrate the Essential® JS 1 Project to Another Version...**
- 
+ 
2. The Project Migration window appears. You can choose the required Syncfusion® version that is installed in the machine that is either Syncfusion® ASP.NET MVC or Syncfusion® ASP.NET MVC (Classic).
- 
+ 
3. The Project Migration window allows you to configure the following options:
@@ -65,7 +65,7 @@ The following steps help you migrate from one version to another version of your
4. Click the Migrate Button. The **Project Backup** dialog will be opened. If click Yes it will backup the current project before migrate the Syncfusion® project. If click No it will migrate the project to required Syncfusion® version without backup.
- 
+ 
5. The Syncfusion® Reference Assemblies, Scripts and CSS are updated to the corresponding version in the project.
diff --git a/Extension/ASPNET-MVC-Extension/Sample-Creator.md b/Extension/ASPNET-MVC-Extension/Sample-Creator.md
index 94ea61b5..cedfeb58 100644
--- a/Extension/ASPNET-MVC-Extension/Sample-Creator.md
+++ b/Extension/ASPNET-MVC-Extension/Sample-Creator.md
@@ -20,30 +20,30 @@ The following steps help you to create the Syncfusion
**Option 1:**
Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ1) > Launch Sample Creator…** in **Visual Studio**.
- 
+ 
N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
**Option 2:**
Launch the Syncfusion® Essential Studio® Dashboard and select the ASP.NET MVC (Essential® JS 1)/ASP.NET MVC (Classic) platform. Select the Sample Creator button to launch the ASP.NET MVC (Essential® JS 1) Sample Creator application. Refer to the following screenshot for more information.
- 
+ 
2. Syncfusion® Sample Creator Wizard displaying the **Controls and its Feature Selection** section.
- 
+ 
### Controls Selection
Listed here are the Syncfusion® ASP.NET MVC controls so you can choose the required controls. And the controls are grouped product wise.
- 
+ 
### Feature Selection
Based on the controls, the Feature is enabled to choose the features of the corresponding controls.
-
+
### Project Configuration
@@ -60,7 +60,7 @@ You can configure the following project details in the Sample Creator.
* Location – Choose the target location of your project.
* Theme Selection – Choose the required theme. The Theme Preview section shows the controls preview before create the Syncfusion® project.
-
+
When you click the Create button, the new Syncfusion® ASP.NET MVC project is created. The following is added in the project:
@@ -70,16 +70,16 @@ When you click the Create button, the new Syncfusion&
* Included the required Syncfusion® ASP.NET MVC scripts and themes files.
- 
+ 
* The required Syncfusion® assemblies are added for selected controls under Project Reference.
- 
+ 
* Configure the Web.Config file by adding the Syncfusion® reference assemblies.
- 
+ 
* Once the project is created you can open the project by clicking the Yes button. Refer the following screenshot for more information.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md b/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md
index d70f4624..1930f733 100644
--- a/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md
+++ b/Extension/ASPNET-MVC-Extension/Step-by-Step-Installation.md
@@ -19,33 +19,33 @@ The following procedure illustrates how to install Syncfusion® Web Sample Creator Setup file. The Self-Extractor Wizard opens and extracts the package automatically.
- 
+ 
N> The WinZip Self-Extractor extracts the syncfusionwebsamplecreator_(version).exe dialog, displaying the unzip operation of the package.
If complete Essential Studio® suite or any of the required Essential Studio® platform setups are installed, Syncfusion® Web Sample Creator setup will be installed.
- 
+ 
If complete Essential Studio® suite or any of the required Essential Studio® platform setups are not installed, Syncfusion® Web Sample Creator setup will show the below message.
- 
+ 
2. After reading the terms, click the I accept the terms and conditions check box.
3. Click the Next button. The Installation location window opens. It shows the Syncfusion® Essential Studio® setup installed location.
- 
+ 
N> It does not allow you to change the install path since its Add on setup for Syncfusion® Essential Studio®.
4. To install it in the displayed default location, click the Install button.
- 
+ 
5. The Completed screen will be displayed once the selected package is installed.
- 
+ 
5. Select the `Run Syncfusion® Control Panel` check box to launch the `Syncfusion® Control Panel` after installed.
diff --git a/Extension/ASPNET-MVC-Extension/Syncfusion-Project-Templates.md b/Extension/ASPNET-MVC-Extension/Syncfusion-Project-Templates.md
index 13db475a..185e5bd1 100644
--- a/Extension/ASPNET-MVC-Extension/Syncfusion-Project-Templates.md
+++ b/Extension/ASPNET-MVC-Extension/Syncfusion-Project-Templates.md
@@ -42,20 +42,20 @@ The following steps help you create the Syncfusion&re
**Option 1:**
Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ1) > Create New Syncfusion® Project…** in **Visual Studio**.
- 
+ 
N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
**Option 2:**
Choose **File > New > Project** and navigate to **Syncfusion® > Web > Syncfusion® ASP.NET MVC (Essential® JS 1) Application** in **Visual Studio**.
- 
+ 
2. Name the Project, choose the destination location as required and set the Framework of the project then click OK. The Project Configuration Wizard appears.
3. Choose the options to configure the Syncfusion® ASP.NET MVC Application by using the following Project Configuration window.
- 
+ 
### Project configurations:
@@ -87,7 +87,7 @@ The following steps help you create the Syncfusion&re
5. By choosing the Add Samples option you can add the code examples for your selected controls and its features.
- 
+ 
**Select Control:** Choose the control based on your need.
@@ -103,7 +103,7 @@ The following steps help you create the Syncfusion&re
7. Syncfusion® references, Scripts, CSS and required Web.config entries are added to the Project.
- 
+ 

@@ -111,7 +111,7 @@ The following steps help you create the Syncfusion&re
8. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
+ 
## Create Syncfusion® MVC (Mobile) Project
@@ -119,12 +119,12 @@ The following steps help you create the Syncfusion&re
1. To create a Syncfusion® Project, choose **New Project -> Syncfusion® -> Mobile -> Syncfusion® ASP.NET MVC(Mobile) Application** from Visual Studio.
- 
+ 
2. Name the Project, choose the destination location as required and set the Framework of the project then click OK. The Project Configuration Wizard appears.
3. Choose the options to configure the Syncfusion® ASP.NET MVC Application by using the following Project Configuration window.
- 
+ 
### Project configurations:
@@ -154,7 +154,7 @@ The following steps help you create the Syncfusion&re
4. Once the Project Configuration Wizard is done, the Syncfusion® MVC Project is created.
- 
+ 
5. Syncfusion® references, Scripts, CSS and required Web.config entries are added to the Project.
@@ -162,8 +162,8 @@ The following steps help you create the Syncfusion&re

- 
+ 
- 
+ 
diff --git a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Scaffolding.md b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Scaffolding.md
index 50aa3b95..d3d3f92f 100644
--- a/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Scaffolding.md
+++ b/Extension/ASPNETCore-EssentialJS2-Extension/Visual-Studio/Scaffolding.md
@@ -25,11 +25,11 @@ The following steps explain you how to add a scaffolded item to your ASP.NET Cor
1. Right-click the **Controllers** folder in the Solution Explorer, click **Add**, and then select **New Scaffolded Item…**
- 
+ 
2. In the **Add Scaffold dialog**, select **Syncfusion® ASP.NET Core UI Scaffolder**, and then click **‘Add’**.
- 
+ 
3. In the Syncfusion® UI Scaffolder dialog, select the desired Syncfusion® control to perform scaffolding, and then click **Next**.
diff --git a/Extension/ASPNETCore-Extension/Overview.md b/Extension/ASPNETCore-Extension/Overview.md
index d73e3c0a..9c9e7ae2 100644
--- a/Extension/ASPNETCore-Extension/Overview.md
+++ b/Extension/ASPNETCore-Extension/Overview.md
@@ -25,15 +25,15 @@ The Syncfusion® provides the following exte
**No project selected in Visual Studio**
-
+
**Selected Microsoft ASP.NET Core application in Visual Studio**
-
+
**Selected Syncfusion® ASP.NET Core (Essential® JS1) application in Visual Studio**
-
+
N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
diff --git a/Extension/ASPNETCore-Extension/Project-Conversion.md b/Extension/ASPNETCore-Extension/Project-Conversion.md
index 2f10ae78..e2a0bf66 100644
--- a/Extension/ASPNETCore-Extension/Project-Conversion.md
+++ b/Extension/ASPNETCore-Extension/Project-Conversion.md
@@ -26,18 +26,18 @@ The following steps help you to use the Syncfusion&re
**Option 1:**
Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ1) > Convert to Syncfusion® ASP.NET Core Application…** in **Visual Studio**.
- 
+ 
N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
**Option 2:**
Right-click the Project from Solution Explorer, select **Syncfusion® Essential® JS 1**, and then choose **Convert to Syncfusion® ASP.NET Core (Essential® JS 1) Application...** Refer to the following screenshot for more information.
- 
+ 
3. Project Conversion Wizard opens to configure the project.
- 
+ 
**Choose the assets from:**
@@ -47,7 +47,7 @@ The following steps help you to use the Syncfusion&re
* Installed Location - Refer to the assets from Syncfusion® installed locations.
- 
+ 
**Choose the Theme:**
@@ -62,17 +62,17 @@ The following steps help you to use the Syncfusion&re

4. Choose the required controls from Components section and Click the **Convert** button to convert it into a Syncfusion® Project.
- 
+ 
The **Project Backup** dialog will be opened. If click Yes it will backup the current project before converting it to Syncfusion® project. If click No it will convert the project to Syncfusion® project without backup.
- 
+ 
5. The required Syncfusion® NuGet/Bower packages, Scripts and CSS are included in the ASP.NET Core Web Application. Refer to the following screenshots for more information.
- 
+ 
- 
+ 
6. If you installed the trial setup or NuGet packages from nuget.org you have to register the Syncfusion® license key to your project since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®.
@@ -82,11 +82,11 @@ Once you converted your ASP.NET Core Web Application to Syncfusion® control snippets to any of the view page of your project. Refer the following screenshot for more information.
- 
+ 
2. Then run the project and the following output will be displayed.
- 
+ 
I> Refer all the required external and internal scripts only once in the page with proper order. Refer this [link](https://help.syncfusion.com/js/control-initialization#adding-the-required-javascript-files) to know about order of script reference.
\ No newline at end of file
diff --git a/Extension/ASPNETCore-Extension/Project-Migration.md b/Extension/ASPNETCore-Extension/Project-Migration.md
index 049e61c7..fcb9d2b5 100644
--- a/Extension/ASPNETCore-Extension/Project-Migration.md
+++ b/Extension/ASPNETCore-Extension/Project-Migration.md
@@ -24,18 +24,18 @@ The following steps help you to migrate your existing Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ1) > Migrate Project…** in **Visual Studio**.
- 
+ 
N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
**Option 2:**
Right-click the **Syncfusion® ASP.NET Core Web Application** from Solution Explorer and select **Syncfusion® Essential® JS 1**. Choose **Migrate the Essential® JS 1 Project to Another Version...**
- 
+ 
2. The **Project Migration** window appears. You can choose the required Essential Studio® version that is installed in the machine.
- 
+ 
3. The **Project Migration** window allows you to configure the following options:
@@ -45,7 +45,7 @@ The following steps help you to migrate your existing Syncfusion® project. If click No it will migrate the project to required Syncfusion® version without backup
- 
+ 
5. The Syncfusion® NuGet/Bower Packages, Scripts and CSS are updated to the corresponding version in the project.
diff --git a/Extension/ASPNETCore-Extension/Sample-Creator.md b/Extension/ASPNETCore-Extension/Sample-Creator.md
index 774e27fc..3b0127f8 100644
--- a/Extension/ASPNETCore-Extension/Sample-Creator.md
+++ b/Extension/ASPNETCore-Extension/Sample-Creator.md
@@ -22,31 +22,31 @@ The following steps help you to create the Syncfusion
**Option 1:**
Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ1) > Launch Sample Creator…** in **Visual Studio**.
- 
+ 
N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
**Option 2:**
Launch the Syncfusion® ASP.NET Core (Essential® JS 1) Control Panel. Select the Sample Creator button to launch the ASP.NET Core (Essential® JS 1) Sample Creator application. Refer to the following screenshot for more information.
- 
+ 
2. Syncfusion® Sample Creator Wizard displaying the **Controls and its Feature Selection** section
- 
+ 
### Controls Selection
Listed here are the Syncfusion® ASP.NET Core controls so you can choose the required controls.
- 
+ 
### Feature Selection
Based on the controls, the Feature is enabled to choose the features of the corresponding controls.
- 
+ 
### Project Configuration
@@ -69,7 +69,7 @@ Based on the controls, the Feature is enabled to choose the features of the corr
* Theme Selection – Choose the required theme.The Theme Preview section shows the controls preview before create the Syncfusion® project.
- 
+ 
2. When you click the Create button, the new Syncfusion® ASP.NET Core project is created. The following resources are added in the project:
@@ -84,8 +84,8 @@ Based on the controls, the Feature is enabled to choose the features of the corr
* Restored the required Syncfusion® NuGet/Bower packages for selected controls under dependencies.
- 
+ 
3. Once the project is created you can open the project by clicking the Yes button. If you click No button the corresponding location of the project will be opened. Refer the following screenshot for more information.
- 
+ 
diff --git a/Extension/ASPNETCore-Extension/Syncfusion-Project-Templates.md b/Extension/ASPNETCore-Extension/Syncfusion-Project-Templates.md
index 808a07fa..e232c2b1 100644
--- a/Extension/ASPNETCore-Extension/Syncfusion-Project-Templates.md
+++ b/Extension/ASPNETCore-Extension/Syncfusion-Project-Templates.md
@@ -24,14 +24,14 @@ The following steps help you to create the **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Core (EJ1) > Create New Syncfusion® Project…** in **Visual Studio**.
- 
+ 
N>In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
**Option 2:**
Choose **File > New > Project** and navigate to **Syncfusion® > .NET Core > Syncfusion® ASP.NET Core (Essential® JS 1) Web Application** in **Visual Studio**.
- 
+ 
2. Name the **Project**, choose the destination location when required and set the Framework of the project, then click **OK**. The Project Configuration Wizard appears.
@@ -51,18 +51,18 @@ The following steps help you to create the **Syncfusion® components to configure.
- 
+ 
4. Once you click Create button, the Syncfusion® ASP.NET Core Application is created.
5. Required Syncfusion® NuGet/Bower packages, Scripts and CSS are added to the Project.
- 
+ 
- 
+ 
6. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
+ 
diff --git a/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Project-Templates.md b/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Project-Templates.md
index f2bfb16d..e0d17c52 100644
--- a/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Project-Templates.md
+++ b/Extension/ASPNETMVC-EssentialJS2-Extension/Syncfusion-Project-Templates.md
@@ -23,7 +23,7 @@ Use the following steps to create the **Syncfusion&re
Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET MVC (EJ2) > Create New Syncfusion® Project…** in **Visual Studio 2019 earlier**.
- 
+ 
> From Visual Studio 2019, Syncfusion® menu is available under Extension in Visual Studio menu.
@@ -33,11 +33,11 @@ Use the following steps to create the **Syncfusion&re
Choose **File > New > Project** and navigate to **Syncfusion® > Web > Syncfusion® ASP.NET MVC (Essential® JS 2) Application** in **Visual Studio 2019 earlier**.
- 
+ 
> In Visual Studio 2019, Syncfusion® ASP.NET MVC will be shown like below in solution explores.
- 
+ 
2. Name the **Project**, choose the destination location, and set the .NET Framework of the project, and then click **OK**. The Project Configuration Wizard appears.
@@ -67,4 +67,4 @@ Use the following steps to create the **Syncfusion&re
5. Then, the Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/whats-new-in-2018-volume-2-licensing-changes-in-the-1620x-version-of-essential-studio.aspx) post to learn more about the licensing changes introduced in Essential Studio®.
- 
+ 
diff --git a/Extension/Blazor-Extension/Visual-Studio-Code/code-snippet.md b/Extension/Blazor-Extension/Visual-Studio-Code/code-snippet.md
index 312b7e26..7bf0b2b5 100644
--- a/Extension/Blazor-Extension/Visual-Studio-Code/code-snippet.md
+++ b/Extension/Blazor-Extension/Visual-Studio-Code/code-snippet.md
@@ -60,6 +60,6 @@ The Syncfusion® Blazor snippet simply inser
4. Open the **~/Startup.cs** file for server application and the **~/Program.cs** file for client application then register the Syncfusion® Blazor Service.
- 
+ 
5. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®.
\ No newline at end of file
diff --git a/Extension/Blazor-Extension/Visual-Studio/scaffolding.md b/Extension/Blazor-Extension/Visual-Studio/scaffolding.md
index 8b6be34d..722e90cf 100644
--- a/Extension/Blazor-Extension/Visual-Studio/scaffolding.md
+++ b/Extension/Blazor-Extension/Visual-Studio/scaffolding.md
@@ -33,7 +33,7 @@ The steps below assist you to how to add a scaffolded item to your Blazor applic
2. In the **Add New Scaffolded item** dialog, select **Syncfusion® Blazor Scaffolder** and then click **‘Add’**.
- 
+ 
3. In the Syncfusion® UI Scaffolder dialog, select the desired control to perform scaffolding, and then click **Next**.
diff --git a/Extension/Document-Viewer-Extension/Visual-Studio-Code/FAQ.md b/Extension/Document-Viewer-Extension/Visual-Studio-Code/FAQ.md
index 64c4a7ee..0d557a2b 100644
--- a/Extension/Document-Viewer-Extension/Visual-Studio-Code/FAQ.md
+++ b/Extension/Document-Viewer-Extension/Visual-Studio-Code/FAQ.md
@@ -11,7 +11,7 @@ documentation: ug
### Can I edit files in the Syncfusion® Document Viewer?
-Yes, the Syncfusion® Document Viewer allows basic editing of Excel, CSV, and TSV files directly within VS Code. This extension focuses on essential® editing tasks to streamline your workflow. For advanced features such as applying formulas, formatting, and complex spreadsheet functions, we recommend using the [Syncfusion® Spreadsheet component](https://www.syncfusion.com/javascript-ui-controls/js-spreadsheet).
+Yes, the Syncfusion® Document Viewer allows basic editing of Excel, CSV, and TSV files directly within VS Code. This extension focuses on essential editing tasks to streamline your workflow. For advanced features such as applying formulas, formatting, and complex spreadsheet functions, we recommend using the [Syncfusion® Spreadsheet component](https://www.syncfusion.com/javascript-ui-controls/js-spreadsheet).
### Is the Syncfusion® Document Viewer suitable for large datasets?
diff --git a/Extension/Document-Viewer-Extension/Visual-Studio-Code/overview.md b/Extension/Document-Viewer-Extension/Visual-Studio-Code/overview.md
index c3e171e9..80dd2f7c 100644
--- a/Extension/Document-Viewer-Extension/Visual-Studio-Code/overview.md
+++ b/Extension/Document-Viewer-Extension/Visual-Studio-Code/overview.md
@@ -11,7 +11,7 @@ documentation: ug
## Overview
-The **Syncfusion® Document Viewer** extension for Visual Studio Code simplifies data handling by integrating essential® features directly into the coding environment. It allows users to view, edit, and manage Excel, CSV, and TSV files without leaving Visual Studio Code.
+The **Syncfusion® Document Viewer** extension for Visual Studio Code simplifies data handling by integrating essential features directly into the coding environment. It allows users to view, edit, and manage Excel, CSV, and TSV files without leaving Visual Studio Code.
## Key Features
diff --git a/Extension/Faq/How-to-get-rid-of-from-multiple-version-alert-message-in-Syncfusion-Xamarin-Toolbox.md b/Extension/Faq/How-to-get-rid-of-from-multiple-version-alert-message-in-Syncfusion-Xamarin-Toolbox.md
index 9499e278..1a5c498c 100644
--- a/Extension/Faq/How-to-get-rid-of-from-multiple-version-alert-message-in-Syncfusion-Xamarin-Toolbox.md
+++ b/Extension/Faq/How-to-get-rid-of-from-multiple-version-alert-message-in-Syncfusion-Xamarin-Toolbox.md
@@ -18,7 +18,7 @@ When dragging and dropping a Syncfusion® co
The following alert message will be displayed if multiple versions of the same Syncfusion® NuGet package (e.g., Syncfusion.Xamarin.SfChart **v24.1.xx** and **v24.2.xx**(xamarin) / Syncfusion.MAUI.Buttons **v24.1.xx** and **24.2.xx**(Maui)) are already installed in your project. Recommend maintaining the same version NuGet reference.
-
+
To resolve this, follow these steps:
1. Uninstall the multiple versions of the same Syncfusion® NuGet package currently installed in your project.
@@ -28,7 +28,7 @@ To resolve this, follow these steps:
The following alert message will be displayed when different versions of Syncfusion® NuGet packages are installed in your project. Hence, you are not aware of which version of the Syncfusion® NuGet package you need to install in your project.
-
+
To resolve this, manually install all the required versions of Syncfusion® NuGet packages in the same version of your project. Then, drag the required Syncfusion® component from the Syncfusion® Toolbox (Xamarin/.NET MAUI) and drop the render code snippet in the XAML file of your project. Please refer to the following help topics to use the Syncfusion® Toolbox:
diff --git a/Extension/Faq/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio.md b/Extension/Faq/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio.md
index d03e9270..1253b920 100644
--- a/Extension/Faq/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio.md
+++ b/Extension/Faq/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio.md
@@ -15,7 +15,7 @@ Perform the given steps to ensure whether the Syncfusion® installed location}\Utilities\Extensions\ASP.NET MVC_
+ _{Syncfusion installed location}\Utilities\Extensions\ASP.NET MVC_
_Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\ASP.NET MVC._
@@ -23,17 +23,17 @@ Perform the given steps to ensure whether the Syncfusion® ASP.NET MVC Extension installed location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img1.png)
+ 
**On or After 17.1.0.32-beta version**
- _{Syncfusion® installed location}\Utilities\Extensions_
+ _{Syncfusion installed location}\Utilities\Extensions_
_Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\ASP.NET MVC - EJ1\18.1.0.52\Utilities\Extensions._
Refer the following screenshot for more information.
- 
+ 
2. When the above path exists, it means that the ASP.NET MVC Extension build has already been installed in the machine. So now you can install the following Syncfusion®
@@ -47,27 +47,27 @@ Perform the given steps to ensure whether the Syncfusion® Build installed location}\Utilities\Extensions\ASP.NET MVC\Project Templates\Web\{Visual Studio Version}_
+ _{Syncfusion Build installed location}\Utilities\Extensions\ASP.NET MVC\Project Templates\Web\{Visual Studio Version}_
Refer the following screenshot.
_Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\ASP.NET MVC\Project Templates\Web\VS2017_
- 
+ 
**On or After 17.1.0.32-beta version**
Navigate to the following location and run the “Syncfusion® Essential JS1 AspNet MVC VSExtensions.vsix” extension.
- _{Syncfusion® Build installed location}\Utilities\Extensions_
+ _{Syncfusion Build installed location}\Utilities\Extensions_
Refer the following screenshot.
_Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\ASP.NET MVC - EJ1\18.1.0.52\Utilities\Extensions_
- 
+ 
## To Install Syncfusion® Visual Studio Extension:
@@ -75,13 +75,13 @@ Perform the given steps to ensure whether the Syncfusion® Web Conversion and Migration.vsix” extension.
- _{Syncfusion® Build installed location}\Utilities\Extensions\Project Conversion\{Visual Studio Version}_
+ _{Syncfusion Build installed location}\Utilities\Extensions\Project Conversion\{Visual Studio Version}_
Refer the following screenshot.
_Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\Project Conversion\VS2017_
- 
+ 
**On or After 17.1.0.32-beta version**
diff --git a/Extension/Frequently-Asked-Questions/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio-How-can-to-get-them-installed.md b/Extension/Frequently-Asked-Questions/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio-How-can-to-get-them-installed.md
index b97f1081..3fcccdd9 100644
--- a/Extension/Frequently-Asked-Questions/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio-How-can-to-get-them-installed.md
+++ b/Extension/Frequently-Asked-Questions/The-Syncfusion-templates-do-not-show-up-in-the-new-project-window-of-Visual-Studio-How-can-to-get-them-installed.md
@@ -13,7 +13,7 @@ Perform the given steps to ensure whether the Syncfusion® installed location}\Utilities\Extensions\ASP.NET MVC_
+ _{Syncfusion installed location}\Utilities\Extensions\ASP.NET MVC_
_Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\ASP.NET MVC._
@@ -21,7 +21,7 @@ Perform the given steps to ensure whether the Syncfusion® Installed location](The-Syncfusion-templatesd_images/The-Syncfusion-templatesd-img1.png)
+ 
2. When the above path exists, it means that the ASP.NET MVC Extension build has already been installed in the machine. So now you can install the following Syncfusion®
@@ -32,24 +32,24 @@ Perform the given steps to ensure whether the Syncfusion® Project Templates:
Navigate to the following location and run the “Syncfusion.MVC.VSPackage.Web.vsix” extension.
- _{Syncfusion® Build installed location}\Utilities\Extensions\ASP.NET MVC\Project Templates\Web\{Visual Studio Version}_
+ _{Syncfusion Build installed location}\Utilities\Extensions\ASP.NET MVC\Project Templates\Web\{Visual Studio Version}_
Refer the following screenshot.
_Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\ASP.NET MVC\Project Templates\Web\VS2017_
- 
+ 
## To Install Syncfusion® Visual Studio Extension:
Navigate to the following Location and run the “Syncfusion® Web Conversion and Migration.vsix” extension.
- _{Syncfusion® Build installed location}\Utilities\Extensions\Project Conversion\{Visual Studio Version}_
+ _{Syncfusion Build installed location}\Utilities\Extensions\Project Conversion\{Visual Studio Version}_
Refer the following screenshot.
_Ex: C:\Program Files (x86)\Syncfusion\Essential Studio\15.4.0.17\Utilities\Extensions\Project Conversion\VS2017_
- 
+ 
diff --git a/Extension/NETMAUI-Extension/Visual-Studio/Toolbox-Control.md b/Extension/NETMAUI-Extension/Visual-Studio/Toolbox-Control.md
index 421d0706..218973a2 100644
--- a/Extension/NETMAUI-Extension/Visual-Studio/Toolbox-Control.md
+++ b/Extension/NETMAUI-Extension/Visual-Studio/Toolbox-Control.md
@@ -25,7 +25,7 @@ To launch the Syncfusion® .NET MAUI Toolbox
5. From the **Essential Studio® for .NET MAUI** submenu, select **Launch .NET MAUI Toolbox**.
This toolbox provides a set of tools and features to easily incorporate Syncfusion® .NET MAUI components into your .NET MAUI application.
- 
+ 
## Launching Syncfusion® .NET MAUI Toolbox from the View menu
@@ -36,12 +36,12 @@ To launch the Syncfusion® .NET MAUI Toolbox
4. In the sub-menu that appears, click on **Syncfusion® .NET MAUI Toolbox**.
This toolbox provides a set of tools and features to easily incorporate Syncfusion® .NET MAUI components into your .NET MAUI application.
- 
+ 
## Add Syncfusion® .NET MAUI Toolbox Components
To incorporate Syncfusion® .NET MAUI components into your XAML design file, you can easily add them by dragging and dropping them from the toolbox. This intuitive approach automatically inserts the component's code sample and namespace into your XAML file, while also taking care of installing necessary NuGet packages.
- 
+ 
Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
\ No newline at end of file
diff --git a/Extension/Syncfusion-NuGet-Packages/NuGet-Packages.md b/Extension/Syncfusion-NuGet-Packages/NuGet-Packages.md
index 9a1f95ea..451b4347 100644
--- a/Extension/Syncfusion-NuGet-Packages/NuGet-Packages.md
+++ b/Extension/Syncfusion-NuGet-Packages/NuGet-Packages.md
@@ -279,7 +279,7 @@ You should get the private Syncfusion® NuGe
2. Click the Copy URL label under required platform to copy the Syncfusion® required platform NuGet feed to clipboard.
- 
+ 
3. Now, use this NuGet feed URL to access the Syncfusion® NuGet Packages in Visual Studio.
@@ -303,7 +303,7 @@ You should get the private Syncfusion® NuGe
5. Click the **Update** button to add the name and source details to package sources.
- 
+ 
#### macOS
@@ -325,7 +325,7 @@ You should get the private Syncfusion® NuGe
For example, Name: Syncfusion® ASP.NET Core Packages, Source: [https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore](https://nuget.syncfusion.com/nuget_aspnetcore/nuget/getsyncfusionpackages/aspnetcore).
- 
+ 
5. Now, click **Add Source** and then click **OK**.
diff --git a/Extension/Syncfusion-NuGet-Packages/Register-the-Syncfusion-License-key.md b/Extension/Syncfusion-NuGet-Packages/Register-the-Syncfusion-License-key.md
index 37eaebd6..bb888969 100644
--- a/Extension/Syncfusion-NuGet-Packages/Register-the-Syncfusion-License-key.md
+++ b/Extension/Syncfusion-NuGet-Packages/Register-the-Syncfusion-License-key.md
@@ -37,4 +37,4 @@ While using Syncfusion® NuGet package of ve
N> You should provide the unlock key which is started with "@" and ended with "=" as a parameter for this Syncfusion® License tool.
- 
+ 
diff --git a/Extension/Syncfusion-NuGet-Packages/Syncfusion-NuGet-Manager.md b/Extension/Syncfusion-NuGet-Packages/Syncfusion-NuGet-Manager.md
index ad7aeeaa..3ed9cfda 100644
--- a/Extension/Syncfusion-NuGet-Packages/Syncfusion-NuGet-Manager.md
+++ b/Extension/Syncfusion-NuGet-Packages/Syncfusion-NuGet-Manager.md
@@ -19,29 +19,29 @@ The following steps directs you to add the Syncfusion
1. Run the SyncfusionNuGetManager.exe from Syncfusion® NuGet Manager extracted location.
- 
+ 
2. Syncfusion® NuGet Manager Window will be opened.
- 
+ 
3. Select the required platforms needed to be configured from “Select platforms to add” (Left side of the window) column and click Add>> button.
- 
+ 
4. Now selected platforms will be added under “Selected platforms to remove” (Right side of the window) column. Click “Configure” button to add the required Syncfusion® Package sources to NuGet Package Manager.
- 
+ 
5. Once Syncfusion® NuGet Manager added the Syncfusion® NuGet sources, the changes will be reflected in package sources of your Visual Studio.
- 
+ 
## Remove Syncfusion® NuGet Package sources
1. If any configured Syncfusion® NuGet Package sources are no longer required, Select the unwanted platforms from “Select platforms to remove” (Right side of the window) column and click <® NuGet Manager to remove the already configured Syncfusion® NuGet feed](SyncfusionNuGetManager_images/SyncfusionNuGetManager-img6.png)
+ 
2. Now selected platforms will be added under “Selected platforms to add” (Left side of the window) column. Click “Configure” button to remove the required Syncfusion® Package sources to NuGet Package Manager.
@@ -57,7 +57,7 @@ The following steps directs you to use the Syncfusion
3. Run SyncfusionNuGetManager.exe with required platforms arguments. Refer the below table for platform as arguments to configure the Syncfusion® NuGet Packages sources.
- 
+ 
**Add**
@@ -152,5 +152,5 @@ Here the list of keyword for platform keys to access.
4. Once Syncfusion® NuGet Manager removed the Syncfusion® NuGet sources, the changes will be reflected in NuGet.config file of your machine and updated the same in available package sources of your Visual Studio.
- 
+ 
diff --git a/Extension/Syncfusion-Reference-Manager/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger.md b/Extension/Syncfusion-Reference-Manager/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger.md
index 04cad6cd..fd14246b 100644
--- a/Extension/Syncfusion-Reference-Manager/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger.md
+++ b/Extension/Syncfusion-Reference-Manager/Add-a-Syncfusion-References-via-Syncfusion-Reference-Manger.md
@@ -16,11 +16,11 @@ To add the assemblies:
1. Select the Syncfusion® Reference Manager either in the WPF, Windows Forms/Console/Class Library or Silverlight Project.
2. The Syncfusion® Reference Manager dialog is displayed as shown in the following screenshot.
- 
+ 
3. If launched the Syncfusion® Reference Manager from Console/Class Library project, Platform selection option will be appeared as option in Syncfusion® Reference Manager. Choose the required platform based on your need.
- 
+ 
N> Platform selection option will be appeared only if Essential Studio® for Enterprise Edition with the platforms WPF and Windows Forms has been installed or both Essential Studio® for WPF and Essential Studio® for Windows Forms has been installed.
@@ -28,38 +28,38 @@ To add the assemblies:
[https://help.syncfusion.com/wpf/themes/skin-manager](https://help.syncfusion.com/wpf/themes/skin-manager)
- 
+ 
N> Themes option will be enabled only if selected SfSkinManager supported controls.
- 
+ 
5. Reference assemblies
* You can add Syncfusion® assemblies from NuGet packages, the build installed location, or by using the GAC location. This option determines the location of the assemblies that are referenced in the project.
N> The installed location and GAC option will be available only when the Syncfusion® Essential Studio® setup has been installed.
- 
+ 
N> The GAC option will not be available if you have selected a .NET 7.0 or .NET 6.0 application in Visual Studio 2022.
* Select the Syncfusion® Essential Studio® versions that were previously installed on your machine.This option determines the assembly version that is referenced in the project.
- 
+ 
* Choose the required controls that you want include in project
6. Click Done to add the required assemblies for the selected controls into the project. The following screenshot shows the list of required assemblies for
the selected controls to be added.
- 
+ 
7. Click OK. The listed Syncfusion® assemblies are added to project. Then it notifies “Syncfusion® assemblies have been added successfully” in Visual Studio status bar.
- 
+ 
8. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
+ 
N> We are providing Syncfusion® Reference Manager support for specific framework which is shipped (assemblies) in our Syncfusion® Essential Studio® setup. So, if we try to add Syncfusion® assemblies in project and project framework is not supported with selected Syncfusion® version assemblies, the dialog will be appeared along with **“Current build v{version} is not supported this framework v{Framework Version}”** message.
diff --git a/Extension/Syncfusion-Reference-Manager/Configure-Syncfusion-assemblies-in-Visual-Studio-project.md b/Extension/Syncfusion-Reference-Manager/Configure-Syncfusion-assemblies-in-Visual-Studio-project.md
index bd9f697c..e0c6fd34 100644
--- a/Extension/Syncfusion-Reference-Manager/Configure-Syncfusion-assemblies-in-Visual-Studio-project.md
+++ b/Extension/Syncfusion-Reference-Manager/Configure-Syncfusion-assemblies-in-Visual-Studio-project.md
@@ -13,7 +13,7 @@ To open Syncfusion® Reference Manager Wizar
**Option 1:**
Click **Syncfusion® Menu** and choose **Essential Studio® for WinForms/WPF > Add References…** or any other Form in **Visual Studio**.
-
+
N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
@@ -22,7 +22,7 @@ Right-click the selected project file from Solution Explorer, then select **Sync
-
+
diff --git a/Extension/Syncfusion-Reference-Manager/Migrate-the-Syncfusion-assemblies.md b/Extension/Syncfusion-Reference-Manager/Migrate-the-Syncfusion-assemblies.md
index 293ab139..ffc1dbaa 100644
--- a/Extension/Syncfusion-Reference-Manager/Migrate-the-Syncfusion-assemblies.md
+++ b/Extension/Syncfusion-Reference-Manager/Migrate-the-Syncfusion-assemblies.md
@@ -18,14 +18,14 @@ To migrate the Syncfusion® assemblies,
3. The dialog Syncfusion® Reference Manager is opened. Then choose the required Syncfusion® Essential Studio® version to migrate the project. Refer the following
screenshots for more information.
- 
+ 
4. When you want to add controls additionally, select controls while the migration is in process. Otherwise, do not select any control.
5. Click Done. The following screenshot shows the list of assemblies to be migrated.
- 
+ 
diff --git a/Extension/Syncfusion-Troubleshooter/Syncfusion-Troubleshooter.md b/Extension/Syncfusion-Troubleshooter/Syncfusion-Troubleshooter.md
index 6ddd2598..98a1cdba 100644
--- a/Extension/Syncfusion-Troubleshooter/Syncfusion-Troubleshooter.md
+++ b/Extension/Syncfusion-Troubleshooter/Syncfusion-Troubleshooter.md
@@ -24,14 +24,14 @@ The following steps help you to utilize the Syncfusion® Application, choose **Syncfusion® menu**. Then select corresponding platform menu and click **Troubleshoot…**
- 
+ 
N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
**Option 2:**
Right-click the Project file in Solution Explorer, then select the command **Syncfusion® Troubleshooter…** Refer to the following screenshot for more information.
- 
+ 
2. Now it’s analyze the project and it will report the project configuration issues of Syncfusion® controls in the Troubleshooter dialog if any issues found. If the project doesn’t have any configuration issue, the dialog box will show there is no configuration changes required in following areas,
@@ -87,17 +87,17 @@ The Syncfusion® Troubleshooter deals with b
**For Instance:** If “Syncfusion.EJ.Export” assembly (v15.2450.0.46) referred in project, But “Syncfusion.EJ.Export” assembly entry version (v15.2450.0.33) in Web.config file. Syncfusion® Troubleshooter will be shown Syncfusion® assembly entry version mismatched.
- 
+ 
2. Multiple version and Duplicate Syncfusion® assembly entry. Syncfusion® Troubleshooter will show the duplicate assembly entry when Syncfusion® assembly entry presented in Web.config which is not referred in project or multiple Syncfusion® assembly entry in Web.config for same Syncfusion® assembly.
**For Instance:** If project have “Syncfusion.EJ.Pivot” assembly (v15.2450.0.43) entry in Web.config file, But “Syncfusion.EJ.Pivot” assembly not referred in project. Syncfusion® Troubleshooter will be show Duplicate assembly entry.
- 
+ 
**For Instance:** If project Multiple “Syncfusion.EJ” assembly (v15.2400.0.46 && v15.2460.0.46) entry with mismatched assembly version/.NET Framework version in Web.config, Syncfusion® Troubleshooter will show the Duplicate assembly entry and Multiple Syncfusion® assembly entries.
- 
+ 
3. Namespace entry missing. If any Syncfusion® namespaces are missing in Web.config that is related to referred Syncfusion® assemblies in project, ® Troubleshooter will show namespace entry is missing.
@@ -109,13 +109,13 @@ The Syncfusion® Troubleshooter deals with b
**For Instance:** If “Syncfusion.EJ” assembly (v15.2450.0.46) referred in project and “Syncfusion.JavaScript.DataVisualization” Namespace entry version (v15.2450.0.43) in Web.config file. Syncfusion® Troubleshooter will be show Syncfusion® namespace entry version mismatched.
- 
+ 
5. HTTP/Server handler entry mismatched. HTTP/Server handler entry version compare to corresponding referred assembly version in project. If any Syncfusion® HTTP/Server handler entry version mismatched, Syncfusion® Troubleshooter will show HTTP/Server handler entry mismatched.
**For Instance:** If “Syncfusion.EJ.” assembly (v15.2450.0.46) referred in project, But “Syncfusion.JavaScript.ImageHandler” HTTP/Server handler entry version (v15.2450.0.43) in Web.config file. Syncfusion® Troubleshooter will be show Syncfusion® HTTP/Server handler entry version mismatched.
- 
+ 
### NuGet Issues
@@ -125,13 +125,13 @@ The Syncfusion® Troubleshooter deals with b
**For Instance:** Syncfusion.Web,Base package installed multiple version(v15.2.0.43 & v15.2.0.46), Syncfusion® Troubleshooter will be shown Syncfusion® package version mismatched.
- 
+ 
2. Installed Syncfusion® NuGet package’s Framework version is differing from the project’s .NET Framework version.
**For Instance:** Syncfusion.Calculate.Base NuGet package version(v15.2.0.46 with 4.0 Framework) installed in project, But the project .NET Framework version is 4.5. So, Syncfusion® Troubleshooter will be show Syncfusion® package Framework version is mismatched.
- 
+ 
3. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing.
@@ -145,16 +145,16 @@ I> Internet connection is required to restore the missing dependent packages. If
1. Once the Syncfusion® Troubleshooter dialog loads, check the corresponding check box of the issue which you need to resolve. Then click the "Fix Issue(s)" button.
- 
+ 
2. A dialog appears, which will ask to take a backup of the project before perform the troubleshooting process. If you need to backup the project before troubleshooting click “Yes” button.
- 
+ 
3. Wait for a while, the Syncfusion® Troubleshooter is being resolve the selected issues. Once the troubleshooting process completed, there will be a status message in the Visual Studio status bar as “Troubleshooting process completed successfully.”
- 
+ 
4. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/whats-new-in-2018-volume-2-licensing-changes-in-the-1620x-version-of-essential-studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/Extension/UWP-Extension/Overview.md b/Extension/UWP-Extension/Overview.md
index 04022ca9..a3f98070 100644
--- a/Extension/UWP-Extension/Overview.md
+++ b/Extension/UWP-Extension/Overview.md
@@ -22,11 +22,11 @@ The Syncfusion® provides the following exte
**No project selected in Visual Studio**
-
+
**Selected Syncfusion® UWP application in Visual Studio**
-
+
N> In Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
diff --git a/Extension/UWP-Extension/Project-Templates.md b/Extension/UWP-Extension/Project-Templates.md
index bacc0ef6..408a9b2a 100644
--- a/Extension/UWP-Extension/Project-Templates.md
+++ b/Extension/UWP-Extension/Project-Templates.md
@@ -24,14 +24,14 @@ The following steps help you to create the **Syncfusion® Menu** and choose **Essential Studio® for UWP > Create New Syncfusion® Project…** in **Visual Studio**.
- 
+ 
N> In Visual Studio 2019, Syncfusion® menu under Extension in Visual Studio menu.
**Option 2:**
Choose **File > New > Project** and navigate to **Syncfusion® > Windows Universal> Syncfusion® Universal Windows Application** in **Visual Studio**.
- 
+ 
2. Name the **Project** and choose the destination location if required, then click **OK**.
@@ -51,7 +51,7 @@ The following steps help you to create the **Syncfusion® components to configure.
- 
+ 
N> If SDK is chosen as the reference type, then all the Syncfusion® UWP controls will be added. So, you no need to select any components.
@@ -59,12 +59,12 @@ The following steps help you to create the **Syncfusion® UWP Application is created with required SDK/references and pages.
- 
+ 
- 
+ 
6. Then, Syncfusion® licensing registration required message box will be shown as follow, if you are installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key) which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
+ 
diff --git a/Extension/WPF-Extension/Add-Item.md b/Extension/WPF-Extension/Add-Item.md
index 0b4796ab..154ca331 100644
--- a/Extension/WPF-Extension/Add-Item.md
+++ b/Extension/WPF-Extension/Add-Item.md
@@ -26,18 +26,18 @@ The following steps will guide you to add the Syncfusion® Item...**.
- 
+ 
**Option 2:**
3. Click **Extensions > Essential Studio® for WPF > Add Syncfusion® Item…** in Visual Studio.
- 
+ 
4. The Syncfusion® WPF Item Template wizard will be launched as follows.
- 
+ 
5. Select the WPF Components from the Component list within your WPF Item Template. The features associated with the selected Component will be presented. From here, choose the specific features that are essential® for your project.
@@ -47,12 +47,12 @@ The following steps will guide you to add the Syncfusion® WPF Item template details](Add-Item-images/Add-Syncfusion-item-3.png)
+ 
8. Click **OK** to incorporate the chosen Components into the WPF application, along with the necessary Syncfusion® assemblies.
- 
+ 
9. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/Extension/WPF-Extension/Add-References.md b/Extension/WPF-Extension/Add-References.md
index c91d1d99..0ff34f37 100644
--- a/Extension/WPF-Extension/Add-References.md
+++ b/Extension/WPF-Extension/Add-References.md
@@ -24,25 +24,25 @@ To add the Syncfusion® assembly references
**Option 1:**
Click **Syncfusion® Menu** and choose **Essential Studio® for WPF > Add References…** in **Visual Studio**.
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
- 
+ 
**Option 2:**
Right-click the selected project file from Solution Explorer, then select **Syncfusion® Reference Manager…** from **Context Menu**. The following screenshot shows this option in Visual Studio.
- 
+ 
3. The Syncfusion® Reference Manager Wizard displays a list of loaded Syncfusion® WPF controls.
- 
+ 
**Platform Selection:** Platform selection option will appear as an option in Syncfusion® Reference Manager if opened from a Console/Class Library project. Select the appropriate platform.
- 
+ 
N> The platform selection option will appear only if Essential Studio® for Enterprise Edition with the platforms WPF and Windows Forms has been installed, or if both Essential Studio® for WPF and WinForms has been installed.
@@ -50,38 +50,38 @@ To add the Syncfusion® assembly references
N> The installed location and GAC option will be available only when the Syncfusion® Essential Studio® WPF setup has been installed.
- 
+ 
N> The GAC option will not be available when you select the WPF (.NET 8.0, .NET 7.0, and.NET 6.0) application in Visual Studio 2022.
**Version:** To add the corresponding version assemblies to the project, select the build version.
- 
+ 
**Themes Option:** Choose the necessary themes based on your requirements. To learn more about built-in themes and their available assembly, click the link below.
[https://help.Syncfusion.com/wpf/themes/](https://help.Syncfusion.com/wpf/themes/)
- 
+ 
N> Themes option will be enabled only if we selected theme supported controls.
- 
+ 
4. Select the required controls you want to add in your project. Then click ****Done** to add the project's required assemblies for the specified controls. The list of required assemblies for the selected controls to be added is shown in the screenshot below.
- 
+ 
5. Click **OK**. The listed Syncfusion® assemblies are added to project. Then it notifies “Syncfusion® assemblies have been added successfully” in Visual Studio status bar.
- 
+ 
6. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
+ 
N> Reference Manager support is provided by Syncfusion® for select versions of the.NET Framework that are included (as assemblies) in the Syncfusion® Essential Studio® installation. If you try to add Syncfusion® assemblies to a project and the project framework isn't compatible with the specified Syncfusion® version assemblies, a dialogue box shows with the message "**Current build v{version} isn't compatible with this framework v{Framework} Version**".
diff --git a/Extension/WPF-Extension/Check-for-Updates.md b/Extension/WPF-Extension/Check-for-Updates.md
index b48d7378..74c09501 100644
--- a/Extension/WPF-Extension/Check-for-Updates.md
+++ b/Extension/WPF-Extension/Check-for-Updates.md
@@ -17,14 +17,14 @@ You can check the availability of updates in Visual Studio and then install the
1. Choose **Syncfusion® -> Check for Updates…** in the Visual Studio menu.
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
- 
+ 
2. When an update is available, the Update dialog box appears.
- 
+ 
3. Syncfusion® Essential Studio® can be downloaded from the Syncfusion® website by clicking the **Download** button.
diff --git a/Extension/WPF-Extension/Create-Project.md b/Extension/WPF-Extension/Create-Project.md
index 0d46d27d..6df2e7ba 100644
--- a/Extension/WPF-Extension/Create-Project.md
+++ b/Extension/WPF-Extension/Create-Project.md
@@ -25,18 +25,18 @@ Create the Syncfusion® WPF project using th
**Option 1:**
Click **Syncfusion®** Menu and choose **Essential Studio® for WPF > Create New Syncfusion® Project…** in **Visual Studio**.
- 
+ 
N> In Visual Studio 2015 or lower, you can see the Syncfusion® menu directly in the Visual Studio menu.
**Option 2:**
Choose **File -> New -> Project**. Opens a new dialog to create a new project. By filtering the project type with Syncfusion® or using the Syncfusion® keyword in the search option, you can get the templates offered by Syncfusion® for WPF.
- 
+ 
In Visual Studio 2015 or lower, Select **File > New > Project** and navigate to **Syncfusion® > Windows > Syncfusion® WPF Application** in Visual Studio.
- 
+ 
2. Name the **Project**, select the destination location when required, and specify the Framework of the project, then click **OK**.
@@ -44,11 +44,11 @@ Create the Syncfusion® WPF project using th
3. Using the following Project Configuration Wizard, choose the options to configure the Syncfusion® WPF Application.
- 
+ 
In Visual Studio 2015 or lower, Syncfusion® WPF Application project configuration wizard.
- 
+ 
**Project Configurations**
@@ -74,12 +74,12 @@ Create the Syncfusion® WPF project using th
4. After choosing above project configuration options in the Project Configuration Wizard, click the create button then Syncfusion® WPF project is created with the necessary XAML files and required Syncfusion® WPF assemblies/NuGet packages.
- 
+ 
- 
+ 
- 
+ 
5. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/Extension/WPF-Extension/Download-and-Installation.md b/Extension/WPF-Extension/Download-and-Installation.md
index 26121155..16b15ddf 100644
--- a/Extension/WPF-Extension/Download-and-Installation.md
+++ b/Extension/WPF-Extension/Download-and-Installation.md
@@ -30,7 +30,7 @@ The steps below assist you to how to install the Syncfusion® extensions from Visual Studio under the Extensions menu.
- 
+ 
## Install from the Visual Studio Marketplace
@@ -44,4 +44,4 @@ The steps below illustrate how to download and install the Syncfusion® extensions from the Visual Studio under the Extensions menu.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/Extension/WPF-Extension/Overview.md b/Extension/WPF-Extension/Overview.md
index 65fa78c0..84a05d61 100644
--- a/Extension/WPF-Extension/Overview.md
+++ b/Extension/WPF-Extension/Overview.md
@@ -30,14 +30,14 @@ The Syncfusion® provides the following exte
**No project selected in Visual Studio**
-
+
**Selected Microsoft WPF application in Visual Studio**
-
+
**Selected Syncfusion® WPF application in Visual Studio**
-
+
N> In Visual Studio 2017 or lower, you can see the Syncfusion® menu directly in the Visual Studio menu.
diff --git a/Extension/WPF-Extension/Template-Studio.md b/Extension/WPF-Extension/Template-Studio.md
index a355d49f..35edb5b5 100644
--- a/Extension/WPF-Extension/Template-Studio.md
+++ b/Extension/WPF-Extension/Template-Studio.md
@@ -27,22 +27,22 @@ Create the Syncfusion® WPF project using th
**Option 1:**
Choose **Extension -> Syncfusion® -> Essential Studio® for WPF -> Create New Syncfusion® Project…** from the Visual Studio menu.
- 
+ 
N> In Visual Studio 2017, you can see the Syncfusion® menu directly in the Visual Studio menu.
**Option 2:**
Choose **File -> New -> Project** from the menu. This launches a new dialogue for creating a new application. Filtering the application type by Syncfusion® or typing Syncfusion® as a keyword in the search option can help you find the Syncfusion® templates for WPF.
- 
+ 
3. Select the Syncfusion® WPF Template Studio and click Next.
- 
+ 
4. When you launch the **Syncfusion® WPF Template Studio**, you will encounter a configuration wizard that allows you to set up your Syncfusion® WPF application. Within this wizard, you will have the option to specify your preferred .NET Core Version or .NET Framework Version, select the desired language(CSharp or Visual Basic), and choose the reference type according to your requirements.
- 
+ 
N> The installed location and GAC options will be available only after the Syncfusion® Essential® WPF setup has been installed. Use the NuGet option instead of installing the Syncfusion® Essential® WPF setup. Also, the GAC option will not be available when you choose .NET 6.0, .NET 7.0, and .NET 8.0 from the project type option in Visual Studio.
@@ -50,17 +50,17 @@ Create the Syncfusion® WPF project using th
5. Click **Next** or navigate to the **Type** tab, then select the desired Syncfusion® WPF application type. When selecting the type of template for your application, you have two options:
- 
+ 
**Predefined template:** Choose this option to select from 5 predefined templates, including Calendar, Contact, Outlook, Docking Manager, Spreadsheet, Tile view, and Word. By choosing one of these templates, you can create your application without needing to follow any further steps.
- 
+ 
**Project type:** Choose this option to select from 4 project types, including Navigation Pane, Blank, Menu Bar, and Ribbon .
6. Click **Next** or navigate to the **Pages** tab to access a list of available Syncfusion® WPF components you can add to the application.
- 
+ 
To unselect the added control(s), Click ‘x’ for the corresponding control in the control list from the Project Details.
@@ -68,21 +68,21 @@ Create the Syncfusion® WPF project using th
7. Click **Next** or navigate to the **Control Features** tab to view the listed features for the selected controls. From here, choose the features needed.
- 
+ 
8. Click **Next** or navigate the **App Features** tab to select the desired application features.
- 
+ 
**Project Details Section**
In the **Project Details** section, you can modify configurations and project types. Additionally, you can remove one or more controls from the selected list and remove the chosen application feature.
-
+
9. Click **Create** to generate the Syncfusion® WPF application. Once you've created the project, the relevant Syncfusion® NuGet packages will be automatically added to your project for the chosen components. For example, if you add an **DataGrid** control, the corresponding Syncfusion® NuGet packages required for that control will be installed.
- 
+ 

@@ -153,4 +153,4 @@ In the **Project Details** section, you can modify configurations and project ty
13. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/Extension/WPF-Extension/Toolbox-Configuration.md b/Extension/WPF-Extension/Toolbox-Configuration.md
index 003eac14..07504bce 100644
--- a/Extension/WPF-Extension/Toolbox-Configuration.md
+++ b/Extension/WPF-Extension/Toolbox-Configuration.md
@@ -27,11 +27,11 @@ To add the Syncfusion® WPF components via t
**Option 2:**
Click **Syncfusion® menu** and choose **Essential Studio® for WPF > Toolbox Configuration...** in **Visual Studio**
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
- 
+ 
2. Toolbox Installer will be opened.
diff --git a/Extension/WPF-Extension/Troubleshooting.md b/Extension/WPF-Extension/Troubleshooting.md
index aba9774a..52591d16 100644
--- a/Extension/WPF-Extension/Troubleshooting.md
+++ b/Extension/WPF-Extension/Troubleshooting.md
@@ -25,17 +25,17 @@ The steps below will assist you in using the Syncfusion® WPF Application, Click **Syncfusion® Menu** and choose **Essential Studio® for WPF > Troubleshoot…** in Visual Studio.
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
- 
+ 
**Option 2**
**Right-click the Project file in Solution Explorer**, then select the command **Syncfusion® Troubleshooter…**
- 
+ 
2. Analyze the project now, and if any Syncfusion® controls project configuration errors are discovered, they will be reported in the Troubleshooter dialog. If there are no configuration issues with the project, the dialog box will indicate that no modifications are required in the following areas:
@@ -89,13 +89,13 @@ The Syncfusion® Troubleshooter addressed fo
**For Instance:** Syncfusion® WPF platform packages installed multiple version (v16.4.0.54 & v17.1.0.38), Syncfusion® Troubleshooter will be shown Syncfusion® package version mismatched.
- 
+ 
2. Installed Syncfusion® NuGet package’s Framework version is differing from the project’s .NET Framework version.
**For Instance:** If “Syncfusion.SfBulletGraph.WPF40” NuGet package version(v15.4.0.17 with 4.0 Framework) installed in project, But the project .NET Framework version is 4.5. So, the Syncfusion® Troubleshooter will show Syncfusion® package Framework version is mismatched.
- 
+ 
3. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing.
@@ -113,28 +113,28 @@ In Syncfusion® projects, the Syncfusion® assembly reference version is v17.1.0.38 but Toolbox assemblies configured v17.1.0.32, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox version mismatched.
- 
+ 
2. If the configured version of Syncfusion® Toolbox differs from the latest Syncfusion® assembly reference version or NuGet package version in the same project, the Syncfusion® Troubleshooter will indicate that the Syncfusion® Toolbox version is mismatched.
**For Instance:** If latest Syncfusion® assembly reference version is v17.1.0.38 but Toolbox assemblies configured v17.1.0.32, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox version mismatched.
- 
+ 
## Apply the solution
1. After loading the Syncfusion® Troubleshooter dialog, check the corresponding check box of the issue to be resolved. Then click the “Fix Issue(s)” button.
- 
+ 
2. A dialog appears, which will ask to take a backup of the project before performing the troubleshooting process. If you need to backup the project before troubleshooting, click “Yes” button.
- 
+ 
3. Wait for a while, the Syncfusion® Troubleshooter is resolving the selected issues. After the troubleshooting process completed, there will be a status message in the Visual Studio status bar as “Troubleshooting process completed successfully”.
- 
+ 
4. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/Extension/WindowsForms-Extension/Add-References.md b/Extension/WindowsForms-Extension/Add-References.md
index e6bb28ec..dc2acfd8 100644
--- a/Extension/WindowsForms-Extension/Add-References.md
+++ b/Extension/WindowsForms-Extension/Add-References.md
@@ -24,49 +24,49 @@ Follow the given steps to add the Syncfusion®® Menu** and choose **Essential Studio® for WinForms > Add References…** or any other Form in **Visual Studio**.
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
**Option 2:**
Right-click the selected project file from Solution Explorer, then select **Syncfusion® Reference Manager…** from **Context Menu**. The following screenshot shows this option in Visual Studio.
- 
+ 
3. The Syncfusion® Reference Manager Wizard that contains the list of Syncfusion® WinForms controls that are loaded.
- 
+ 
**Platform Selection:** If launched the Syncfusion® Reference Manager from Console/Class Library project, Platform selection option will be appeared as option in Syncfusion® Reference Manager. Choose the required platform.
- 
+ 
**Assembly From:** Choose the assembly location, either from NuGet packages, the build installed location, or by using the GAC location.
N> The installed location and GAC option will be available only when the Syncfusion® Essential Studio® Winforms setup has been installed.
- 
+ 
N> The GAC option will not be available if you have selected a WinForms (.NET 8.0, .NET 7.0, and .NET 6.0) application in Visual Studio 2022.
**Version:** Choose the build version to add the corresponding version assemblies to the project.
- 
+ 
4. Choose the required controls that you want to include in the project. Then, click Done to add the required assemblies for the selected controls into the project. The following screenshot shows the list of required assemblies for the selected controls to be added.
- 
+ 
5. Click **OK**. The listed Syncfusion® assemblies are added to project. Then it notifies “Syncfusion® assemblies have been added successfully” in Visual Studio status bar.
- 
+ 
6. Then, Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusio.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
+ 
N> Syncfusion® provides Reference Manager support for specific .NET Framework, which is shipped (assemblies) in Syncfusion® Essential Studio® setup. So, if you try to add Syncfusion® assemblies in the project and project framework is not supported with selected Syncfusion® version assemblies, the dialog appears along with **“Current build v{version} is not supported this framework v{Framework Version}”** message.
diff --git a/Extension/WindowsForms-Extension/Check-for-Updates.md b/Extension/WindowsForms-Extension/Check-for-Updates.md
index 0313b2e2..23945159 100644
--- a/Extension/WindowsForms-Extension/Check-for-Updates.md
+++ b/Extension/WindowsForms-Extension/Check-for-Updates.md
@@ -17,12 +17,12 @@ You can check updates availability in Visual Studio, and then install the update
1. Choose **Syncfusion® -> Check for Updates…** in the Visual Studio menu
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
2. When there is an update, **Update** dialog box opens.
- 
+ 
3. You can download the latest Syncfusion® Essential Studio® from the Syncfusion® website by selecting **Download**.
diff --git a/Extension/WindowsForms-Extension/Overview.md b/Extension/WindowsForms-Extension/Overview.md
index 4a491b1d..389a96e0 100644
--- a/Extension/WindowsForms-Extension/Overview.md
+++ b/Extension/WindowsForms-Extension/Overview.md
@@ -27,15 +27,15 @@ The Syncfusion® provides the following exte
**No project selected in Visual Studio**
-
+
**Selected Microsoft Windows Forms application in Visual Studio**
-
+
**Selected Syncfusion® Windows Forms application in Visual Studio**
-
+
N> From Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
diff --git a/Extension/WindowsForms-Extension/Syncfusion-Item-Templates-for-Windows-Forms.md b/Extension/WindowsForms-Extension/Syncfusion-Item-Templates-for-Windows-Forms.md
index 9ea6ed8f..3a2ffd8c 100644
--- a/Extension/WindowsForms-Extension/Syncfusion-Item-Templates-for-Windows-Forms.md
+++ b/Extension/WindowsForms-Extension/Syncfusion-Item-Templates-for-Windows-Forms.md
@@ -25,18 +25,18 @@ The following steps will guide you in adding the Syncfusion® Item...**.
- 
+ 
**Option 2:**
3. Click **Extensions > Essential Studio® for WinForms > Add Syncfusion® Item…** in Visual Studio.
- 
+ 
4. The Syncfusion® WinForms Item Template wizard will be launched as follows.
- 
+ 
5. Select the WinForms Components from the Component list within your WinForms Item Template. The features associated with the selected Component will be presented. From here, choose the specific features that are essential for your project.
@@ -46,12 +46,12 @@ The following steps will guide you in adding the Syncfusion® WinForms Item template details](Item-Template-images/Add-Syncfusion-item-3.png)
+ 
8. Click **OK** to incorporate the chosen Components into the WinForms application, along with the necessary Syncfusion® assemblies.
- 
+ 
9. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/Extension/WindowsForms-Extension/Syncfusion-Project-Templates-for-Windows-Forms.md b/Extension/WindowsForms-Extension/Syncfusion-Project-Templates-for-Windows-Forms.md
index 283475aa..56e2599b 100644
--- a/Extension/WindowsForms-Extension/Syncfusion-Project-Templates-for-Windows-Forms.md
+++ b/Extension/WindowsForms-Extension/Syncfusion-Project-Templates-for-Windows-Forms.md
@@ -24,18 +24,18 @@ Use the following steps to create the Syncfusion®
**Option 1:**
Click **Syncfusion® Menu** and choose **Essential Studio® for WinForms > Create New Syncfusion® Project…** in **Visual Studio**.
- 
+ 
N> In Visual Studio 2015 or lower, you can see the Syncfusion® menu directly in the Visual Studio menu.
**Option 2:**
Choose **File -> New -> Project**. Opens a new dialog to create a new project. You can obtain the templates provided by Syncfusion® for WinForms by filtering the project type with Syncfusion® or by using the Syncfusion® keyword in the search option
- 
+ 
In Visual Studio 2015 or lower, Select File > New > Project and navigate to Syncfusion® > Windows > Syncfusion® Windows Forms Application in Visual Studio.
- 
+ 
2. Name the **Project**, choose the destination location when required, select the project type, and choose the reference from where the assembly is added to the project then click **OK**.
@@ -43,11 +43,11 @@ Use the following steps to create the Syncfusion®
3. Choose the options to configure the Syncfusion® WinForms Application by using the following Project Configuration Wizard.
- 
+ 
In Visual Studio 2015 or lower, Syncfusion® Windows Forms Application project configuration wizard.
- 
+ 
**Project Configurations**
@@ -67,12 +67,12 @@ Use the following steps to create the Syncfusion®
4. After choosing above project configuration options in the Project Configuration Wizard, click the create button then Syncfusion® WinForms project is created with the necessary XAML files and required Syncfusion® WinForms assemblies/NuGet packages.
- 
+ 
- 
+ 
- 
+ 
5. Then, the Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post to learn more the licensing changes introduced in Essential Studio®.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/Extension/WindowsForms-Extension/Template-Studio.md b/Extension/WindowsForms-Extension/Template-Studio.md
index 09213675..840e5e0b 100644
--- a/Extension/WindowsForms-Extension/Template-Studio.md
+++ b/Extension/WindowsForms-Extension/Template-Studio.md
@@ -27,22 +27,22 @@ Create the Syncfusion® WinForms project usi
**Option 1:**
Choose **Extension -> Syncfusion® -> Essential Studio® for WinForms -> Create New Syncfusion® Project…** from the Visual Studio menu.
- 
+ 
N> In Visual Studio 2017, you can see the Syncfusion® menu directly in the Visual Studio menu.
**Option 2:**
Choose **File -> New -> Project** from the menu. This launches a new dialogue for creating a new application. Filtering the application type by Syncfusion® or typing Syncfusion® as a keyword in the search option can help you find the Syncfusion® templates for WinForms.
- 
+ 
3. Select the **Syncfusion® WinForms Template Studio** and click Next.
- 
+ 
4. When you launch the **Syncfusion® WinForms Template Studio**, you will encounter a configuration wizard that allows you to set up your Syncfusion® WinForms application. Within this wizard, you will have the option to specify your preferred .NET Core Version or .NET Framework Version, select the desired language(CSharp or Visual Basic), and choose the reference type according to your requirements.
- 
+ 
N> The installed location and GAC options will be available only after the Syncfusion® Essential WinForms setup has been installed. Use the NuGet option instead of installing the Syncfusion® Essential WinForms setup. Also, the GAC option will not be available when you choose .NET 6.0, .NET 7.0, and .NET 8.0 from the project type option in Visual Studio.
@@ -50,17 +50,17 @@ Create the Syncfusion® WinForms project usi
5. Navigate to the **Type** tab and choose the Syncfusion® WinForms application type you want. When selecting the type of template for your application, you have two options:
- 
+ 
**Predefined template:** Choose this option to select from 5 predefined templates, including Calendar, Contact, Outlook, Docking Manager, and Spreadsheet. By choosing one of these templates, you can create your application without needing to follow any further steps.
- 
+ 
**Project type:** Choose this option to select from 4 project types, including Blank, Menu Bar, Ribbon, and Tabbed Form.
6. Click **Next** or navigate to the **Pages** tab to access a list of available Syncfusion® WinForms components you can add to the application.
- 
+ 
To unselect the added control(s), Click ‘x’ for the corresponding control in the control list from the Project Details.
@@ -68,11 +68,11 @@ Create the Syncfusion® WinForms project usi
7. Click **Next** or navigate to the **Control Features** tab to view the listed features for the selected controls. From here, choose the features needed.
- 
+ 
8. Click **Next** or navigate the **App Features** tab to select the desired application features.
- 
+ 
N> The App Features option is not accessible for .NET Framework.
@@ -80,11 +80,11 @@ Create the Syncfusion® WinForms project usi
In the **Project Details** section, modify configurations and project types. Additionally, you can remove one or more controls from the selected list and remove the chosen application feature.
- 
+ 
9. Click **Create** to generate the Syncfusion® WinForms application. Once you've created the project, the relevant Syncfusion® NuGet packages will be automatically added to your project for the chosen components. For example, if you add an **DataGrid** control, the corresponding Syncfusion® NuGet packages required for that control will be installed.
- 
+ 

@@ -154,4 +154,4 @@ Here's a simple explanation:
13. If you install the trial setup or NuGet packages from nuget.org, you must register the Syncfusion® license key to your application since Syncfusion® introduced the licensing system from the 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-Syncfusion-license-key) to generate and register the Syncfusion® license key to your application. Refer to this [blog](https://www.Syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/Extension/WindowsForms-Extension/Toolbox-Configuration.md b/Extension/WindowsForms-Extension/Toolbox-Configuration.md
index 07bae4eb..5742bc9a 100644
--- a/Extension/WindowsForms-Extension/Toolbox-Configuration.md
+++ b/Extension/WindowsForms-Extension/Toolbox-Configuration.md
@@ -27,7 +27,7 @@ Use the following steps to add the Syncfusion®® menu** and choose **Essential Studio® for WinForms > Toolbox Configuration...** in **Visual Studio**.
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
diff --git a/Extension/WindowsForms-Extension/Troubleshooting.md b/Extension/WindowsForms-Extension/Troubleshooting.md
index dc55fe2e..498518e8 100644
--- a/Extension/WindowsForms-Extension/Troubleshooting.md
+++ b/Extension/WindowsForms-Extension/Troubleshooting.md
@@ -25,14 +25,14 @@ The following steps help you to utilize the Syncfusion® WinForms Application, Click **Syncfusion® Menu** and choose **Essential Studio® for WinForms > Troubleshoot…** in Visual Studio.
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
**Option 2:**
Right-click the Project file in Solution Explorer, then select the command Syncfusion® Troubleshooter…
- 
+ 
2. Analyze the project now, and if any Syncfusion® controls project configuration errors are discovered, they will be reported in the Troubleshooter dialog. If there are no configuration issues with the project, the dialog box will indicate that no modifications are required in the following areas:
@@ -86,13 +86,13 @@ The Syncfusion® Troubleshooter deals with t
**For Instance:** Syncfusion® WinForms platform packages installed multiple version (v16.4.0.54 & v17.1.0.38), Syncfusion® Troubleshooter will be shown Syncfusion® package version mismatched.
- 
+ 
2. Installed Syncfusion® NuGet package’s Framework version is differing from the project’s .NET Framework version.
**For Instance:** Syncfusion®.SfBulletGraph.Windows40 NuGet package version(v15.2.0.17 with 4.0 Framework) installed in project, But the project .NET Framework version is 4.5. So, the Syncfusion® Troubleshooter will show Syncfusion® package Framework version is mismatched.
- 
+ 
3. Dependent NuGet package of the installed Syncfusion® NuGet packages is missing.
@@ -110,28 +110,28 @@ The Syncfusion® Troubleshooter deals with t
**For Instance:** The project .NET Framework version is 4.5 and Syncfusion® Toolbox is not configured 4.6 framework assemblies only in corresponding Visual Studio, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox framework version mismatched.
- 
+ 
2. If Syncfusion® Toolbox configured version is differed from latest Syncfusion® assembly reference version or NuGet package version in same project, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox version is mismatched.
**For Instance:** If latest Syncfusion® assembly reference version is v17.1.0.38 but Toolbox assemblies configured v17.1.0.32, the Syncfusion® Troubleshooter will show Syncfusion® Toolbox version mismatched.
- 
+ 
## Apply the solution
1. After loading the Syncfusion® Troubleshooter dialog, check the corresponding check box of the issue to be resolved. Then click the “Fix Issue(s)” button.
- 
+ 
2. A dialog appears, which will ask to take a backup of the project before performing the troubleshooting process. If you need to backup the project before troubleshooting, click “Yes” button.
- 
+ 
3. Wait for a while, the Syncfusion® Troubleshooter is resolving the selected issues. After the troubleshooting process completed, there will be a status message in the Visual Studio status bar as “Troubleshooting process completed successfully”.
- 
+ 
4. Then, Syncfusion® licensing registration required message box will be shown, if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.Syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-Syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.Syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/Extension/Xamarin-Extension/Check-for-Updates.md b/Extension/Xamarin-Extension/Check-for-Updates.md
index fd8b41b2..67e966f4 100644
--- a/Extension/Xamarin-Extension/Check-for-Updates.md
+++ b/Extension/Xamarin-Extension/Check-for-Updates.md
@@ -17,14 +17,14 @@ You can check updates availability in Visual Studio, and then install the update
1. Choose **Syncfusion® -> Check for Updates…** in the Visual Studio menu
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
- 
+ 
2. When an update is available, the Update dialog box appears.
- 
+ 
3. You can download the Syncfusion® Essential Studio® from the Syncfusion® website by selecting **Download**.
diff --git a/Extension/Xamarin-Extension/Create-Project.md b/Extension/Xamarin-Extension/Create-Project.md
index 58284232..31ebd333 100644
--- a/Extension/Xamarin-Extension/Create-Project.md
+++ b/Extension/Xamarin-Extension/Create-Project.md
@@ -22,26 +22,26 @@ To create the **Syncfusion® Xamarin Applica
**Option 1:**
Click **Syncfusion® Menu** and choose **Essential Studio® for Xamarin > Create New Syncfusion® Project…** in **Visual Studio**.
- 
+ 
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
- 
+ 
**Option 2:**
Choose **File > New > Project** and navigate to **Syncfusion® > Cross-Platform > Syncfusion® Xamarin Project Template** in **Visual Studio**.
- 
+ 
In Visual Studio 2019, Syncfusion® Xamarin project creation wizard like below.
- 
+ 
2. Click **OK** once you've given the **project name**, selected a destination location, and set the project's Framework. The Project Configuration Wizard is now displayed.
3. Choose the Project, Android, iOS, and UWP by on/off in the following Project Configuration window to configure the Syncfusion® Xamarin Application.
- 
+ 
**Project Configuration:**
@@ -63,42 +63,42 @@ To create the **Syncfusion® Xamarin Applica
N> If you want to add other Syncfusion® Xamarin controls in the created Syncfusion® Xamarin application, you can use our [Syncfusion® Xamarin toolbox](https://help.syncfusion.com/xamarin/visual-studio-integration/toolbox-control)
- 
+ 
4. The Syncfusion® Xamarin Application has been created when you click **Create**.
N> Choose any one of the project type and controls from Project Configuration Wizard.
- 
+ 
5. Based on the control selected, required Syncfusion® NuGet/Assemblies and configuration have been added to the project.
**Net Standard /PCL**
- 
+ 
- 
+ 
**Android**
- 
+ 
- 
+ 
**iOS**
- 
+ 
- 
+ 
**UWP**
- 
+ 
- 
+ 
6. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
- 
+ 
diff --git a/Extension/Xamarin-Extension/Download-and-Installation.md b/Extension/Xamarin-Extension/Download-and-Installation.md
index e868d14f..ca475922 100644
--- a/Extension/Xamarin-Extension/Download-and-Installation.md
+++ b/Extension/Xamarin-Extension/Download-and-Installation.md
@@ -30,7 +30,7 @@ The steps below assist you to how to install the Syncfusion® extensions from Visual Studio under the Extensions menu.
- 
+ 
## Install from the Visual Studio Marketplace
@@ -44,4 +44,4 @@ The steps below illustrate how to download and install the Syncfusion® extensions from the Visual Studio under the Extensions menu.
- 
\ No newline at end of file
+ 
\ No newline at end of file
diff --git a/Extension/Xamarin-Extension/Essential-UI-Kit.md b/Extension/Xamarin-Extension/Essential-UI-Kit.md
index 9c282661..fc0aaada 100644
--- a/Extension/Xamarin-Extension/Essential-UI-Kit.md
+++ b/Extension/Xamarin-Extension/Essential-UI-Kit.md
@@ -21,7 +21,7 @@ Install the appropriate [Xamarin UI Kit Extension](https://marketplace.visualstu
2. Select the **Essential® UI Kit for Xamarin.Forms** from the **Solution Explorer** by right-clicking on your **Xamarin.Forms** project
- 
+ 
N> The Essential® UI Kit for Xamarin.Forms add-in will be shown when the project has the Xamarin.Forms NuGet package as a reference and also, Xamarin.Forms project should be a NET Standard project.
diff --git a/Extension/Xamarin-Extension/Overview.md b/Extension/Xamarin-Extension/Overview.md
index edbbda94..5f3574fe 100644
--- a/Extension/Xamarin-Extension/Overview.md
+++ b/Extension/Xamarin-Extension/Overview.md
@@ -25,10 +25,10 @@ The Syncfusion® provides the following exte
**No project selected in Visual Studio**
-
+
**Selected Microsoft/Syncfusion® Xamarin (Xamarin.Forms) application in Visual Studio**
-
+
N> From Visual Studio 2019, Syncfusion® menu available under Extension in Visual Studio menu.
diff --git a/Extension/Xamarin-Extension/Toolbox.md b/Extension/Xamarin-Extension/Toolbox.md
index 4f9da9a9..947536f3 100644
--- a/Extension/Xamarin-Extension/Toolbox.md
+++ b/Extension/Xamarin-Extension/Toolbox.md
@@ -21,29 +21,29 @@ I> The Syncfusion® Xamarin Toolbox is avail
To launch the Syncfusion® Toolbox from Visual Studio 2019 and later, click **Extensions** in Visual Studio menu and choose **Syncfusion® > Essential Studio® for Xamarin > Launch Toolbox…**
- 
+ 
**Visual Studio 2017**
To launch the Syncfusion® Toolbox from Visual Studio 2017, click **Syncfusion®** in Visual Studio menu and choose **Essential Studio® for Xamarin > Launch Toolbox...**
- 
+ 
## Launching Syncfusion® Xamarin Toolbox from View menu
To launch the Visual Studio Toolbox from Visual Studio menu in Visual Studio 2017 and later, click **View > Other Windows > Syncfusion® Toolbox** in Visual Studio.
- 
+ 
> You can also find the Syncfusion® Toolbox option by typing "Syncfusion® Toolbox" into the Quick Launch search field (top right corner in Visual Studio).
- 
+ 
## Render Syncfusion® components
1. When you click the Syncfusion® Toolbox window, the Syncfusion® Toolbox wizard is launched, and Syncfusion® components are enabled once you access your application's designer page (XAML). Syncfusion® components will not appear until open the appropriate design (XAML) file from the Xamarin shared/.NET Standard/PCL project. The rendering of the Syncfusion® Xamarin components is made as simple as possible. All you need to do simply dragging and dropping the Syncfusion® Xamarin component from the Syncfusion® toolbox into the designer. The selected component's code snippet and namespace will be added to the designer page(XAML) and the required Syncfusion® Xamarin NuGet packages will be installed.
- 
+ 
2. Then, Syncfusion® licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion® introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio® release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
\ No newline at end of file