|
|
-TabbedMdI Manager |
+TabbedMDI Manager |
TabMove |
- |
Click |
diff --git a/WindowsForms/Upgrade/how-to-upgrade-syncfusion-components-using-vs-extensions.md b/WindowsForms/Upgrade/how-to-upgrade-syncfusion-components-using-vs-extensions.md
index f4ab8764e..0b9acdf91 100644
--- a/WindowsForms/Upgrade/how-to-upgrade-syncfusion-components-using-vs-extensions.md
+++ b/WindowsForms/Upgrade/how-to-upgrade-syncfusion-components-using-vs-extensions.md
@@ -1,28 +1,36 @@
---
layout: post
-title: Upgrading Syncfusion WinForms components to a latest version
+title: Upgrading Syncfusion WinForms components to the latest version
description: Learn here about the how upgrade Syncfusion WinForms components to a latest version from NuGet manager and migrate.
platform: WindowsForms
control: Essential Studio
documentation: ug
---
-# Upgrading Syncfusion Windows Forms components to latest version
+# Upgrading Syncfusion Windows Forms components to the latest version
-Syncfusion publishes the Visual Studio extension in the [Visual Studio marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Windows-Extensions) for every Syncfusion Volume releases, with exciting new features and Service Pack release with major bug fixes in the volume releases.
+Syncfusion publishes the Visual Studio extension in the [Visual Studio marketplace](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Windows-Extensions) for every Syncfusion Volume release, with exciting new features, and a Service Pack release with major bug fixes in the volume release.
You can upgrade to our latest version from any installed Syncfusion version.
## Upgrading to the latest version
-1. In Visual Studio go to Extensions -> Manage Extensions -> Updates and find the Syncfusion WinForms extension.
+Before starting the upgrade, close all Visual Studio instances and stop any running debugging sessions. Updating the extension while Visual Studio is running requires closing Visual Studio during the install step.
- N> In Visual Studio 2017 or lower, go to Tools -> Extensions and Updates.
+1. In Visual Studio go to **Extensions -> Manage Extensions -> Updates** and find the Syncfusion WinForms extension.
-2. Then, click on the Update button to update the extension.
+ N> In Visual Studio 2017 or earlier, go to **Tools -> Extensions and Updates**.
+
+2. Then, click on the **Update** button to update the extension.
-3. Now close the Visual Studio and click on the Modify button in VSIX installer dialog.
+3. Close Visual Studio and click **Modify** in the VSIX installer dialog.
+
+ 
+
+4. After the VSIX installer finishes, restart Visual Studio. Open **Extensions -> Manage Extensions -> Installed** and verify the Syncfusion WinForms extension shows the new version.
+
+### Toolbox recovery
- 
\ No newline at end of file
+If the Syncfusion toolbox controls disappear after the extension update, run the Syncfusion installer (or re-run the extension installer) with the **Configure Syncfusion controls in Visual Studio** option enabled. This re-registers the toolbox items for the current Visual Studio version.
\ No newline at end of file
diff --git a/WindowsForms/Upgrade/how-to-upgrade.md b/WindowsForms/Upgrade/how-to-upgrade.md
index bf94c9268..f07e53f8c 100644
--- a/WindowsForms/Upgrade/how-to-upgrade.md
+++ b/WindowsForms/Upgrade/how-to-upgrade.md
@@ -1,13 +1,13 @@
---
layout: post
-title: Upgrading Syncfusion Windows Forms installer to latest version
+title: Upgrading Syncfusion Windows Forms installer to the latest version
description: Learn here about the how upgrade Syncfusion Windows Forms installer to a latest version from website and control panel.
platform: WindowsForms
control: Essential Studio
documentation: ug
---
-# Upgrading Syncfusion Windows Forms installer to a latest version
+# Upgrading Syncfusion Windows Forms installer to the latest version
Syncfusion releases new volumes once every three months, with exciting new features. There will be one Service Pack release for these volume releases. Service Pack releases are provided to address major bug fixes in the volume releases.
@@ -18,13 +18,14 @@ See our "[**Upgrade Guide**](https://help.syncfusion.com/upgrade-guide/winforms-
## Upgrading to the latest version
+Before starting the upgrade, close all Visual Studio instances and any running Syncfusion applications.
+
The most recent version of Syncfusion Windows Forms can be downloaded and installed by clicking on the "Latest Version: {Version}" link at the top of the Syncfusion Windows Forms Control Panel.
You can also upgrade to the latest version just by downloading and installing the products you require from [this](https://www.syncfusion.com/account/downloads) link. The existing installed versions are not required to be uninstalled.
-
It is not required to install the Volume release before installing the Service Pack release. As releases for Volume and Service Packs work independently, you can install the latest version with major bug fixes directly.
@@ -35,5 +36,4 @@ To upgrade from trial version, there are two possible solutions.
* Uninstall the trial version and install the fully licensed build from the [License & Downloads](https://www.syncfusion.com/account/downloads) section of our website.
* If you are using Syncfusion controls from [nuget.org](https://www.nuget.org/packages?q=syncfusion), replace the currently used trial license key with a paid license key that can be generated from the [License & Downloads](https://www.syncfusion.com/account/downloads) section of our website. Refer to [this](https://help.syncfusion.com/windowsforms/licensing/how-to-register-in-an-application) topic for more information regarding registering the license in the application.
-N> License registration is not required if you reference Syncfusion assemblies from Licensed installer. These licensing changes applicable to all evaluators who refers the Syncfusion assemblies from evaluation installer and those who use Syncfusion NuGet packages from [nuget.org](https://www.nuget.org/packages?q=syncfusion).
-
+N> License registration is not required if you reference Syncfusion assemblies from Licensed installer. These licensing changes applicable to all evaluators who refers the Syncfusion assemblies from evaluation installer and those who use Syncfusion NuGet packages from [nuget.org](https://www.nuget.org/packages?q=syncfusion).
\ No newline at end of file
diff --git a/WindowsForms/Upgrade/upgrade-syncfusion-winforms-nuget-packages.md b/WindowsForms/Upgrade/upgrade-syncfusion-winforms-nuget-packages.md
index a50c4bc65..6a32c3ff0 100644
--- a/WindowsForms/Upgrade/upgrade-syncfusion-winforms-nuget-packages.md
+++ b/WindowsForms/Upgrade/upgrade-syncfusion-winforms-nuget-packages.md
@@ -1,17 +1,17 @@
---
layout: post
-title: Upgrade Syncfusion WinForms NuGet packages to a latest version
-description: Learn here about the how to upgrading Syncfusion WinForms NuGet packages to a latest version using NuGet manager and package manager UI.
+title: Upgrade Syncfusion WinForms NuGet packages to the latest version
+description: Learn here about the how to upgrade Syncfusion WinForms NuGet packages to the latest version using the NuGet manager and package manager UI.
platform: WindowsForms
control: Essential Studio
documentation: ug
---
-# Upgrading Syncfusion WinForms NuGet packages to a latest version
+# Upgrading Syncfusion WinForms NuGet packages to the latest version
Every three months, Syncfusion releases new volumes with interesting new features. For this volume, there will be weekly NuGet releases and a service pack. Syncfusion WinForms NuGet packages are released on a weekly basis to address critical issue fixes.
-From any Syncfusion WinForms NuGet version you have installed; you can update to our most recent version.
+From any Syncfusion WinForms NuGet version you have installed, you can update to our most recent version.
## Upgrade NuGet packages through Package Manager UI
@@ -27,13 +27,15 @@ The NuGet **Package Manager UI** in Visual Studio allows you to easily install,
> The [nuget.org](https://api.nuget.org/v3/index.json) package source is selected by default in the Package source drop-down. If your Visual Studio does not have nuget.org configured, follow the instructions in the [Microsoft documents](https://docs.microsoft.com/en-us/nuget/tools/package-manager-ui#package-sources) to set up the nuget.org feed URL.
-3. By default, the package selected with latest version. You can select the required version and click the **Update** button and accept the license terms. The package will be upgraded to selected version in your WinForms application.
+3. By default, the package is selected with the latest version. You can select the required version and click the **Update** button and accept the license terms. The package will be upgraded to the selected version in your WinForms application.
You can choose the multiple NuGet packages by selecting the checkbox like below and click the **Update** button to update the multiple Syncfusion NuGet packages in your application.
- 
+ 
+
+4. After the upgrade, perform a **Clean** and then **Rebuild** of the solution. Verify the upgraded version in the `.csproj`/`.vbproj` file or in the **Installed** tab of the NuGet Package Manager.
## Upgrade NuGet packages through .NET CLI
@@ -48,31 +50,32 @@ To specify a version, add the -v parameter:
The **Package Manager Console** saves NuGet packages upgrade time since you don't have to search for the package you want to update, and you can just type the command to update the appropriate Syncfusion WinForms NuGet package. Follow the steps below to upgrade the installed Syncfusion NuGet packages using the Package Manager Console in your WinForms application.
1. To show the Package Manager Console, open your WinForms application in Visual Studio and navigate to **Tools** in the Visual Studio menu and after hovering **NuGet Package Manager**, select **Package Manager Console**.
-
-2. The Package Manager Console will be shown at the bottom of the screen. You can install the Syncfusion WinForms NuGet packages by enter the following NuGet update commands.
+2. The **Package Manager Console** will be shown at the bottom of the screen. You can update the Syncfusion WinForms NuGet packages by entering the following NuGet update commands.
- ***Update specified Syncfusion WinForms NuGet package***
+ ### Updating a specified Syncfusion WinForms NuGet package
- The below command will update the Syncfusion WinForms NuGet package in the default WinForms application
+ The command below updates the Syncfusion WinForms NuGet package in the default WinForms application.
```Update-Package ```
**For example:** Update-Package Syncfusion.Grid.Windows
- ***Update specified Syncfusion WinForms NuGet package in specified WinForms application***
+ ### Updating a specified Syncfusion WinForms NuGet package in a specified WinForms application
- The below command will update the Syncfusion WinForms NuGet package in the given WinForms application alone
+ The command below updates the Syncfusion WinForms NuGet package in the given WinForms application.
```Update-Package -ProjectName ```
- **For example:** Update-Package Syncfusion.Grid.Windows -ProjectName SyncfusionWinformsApp
+ **For example:** `Update-Package Syncfusion.Grid.Windows -ProjectName SyncfusionWinformsApp`
3. By default, the package will be installed with latest version. You can give the required version with the -Version term like below to install the Syncfusion WinForms NuGet packages in the appropriate version.
- ```Update-Package Syncfusion.Grid.Windows -Version 19.2.0.59```
+ ```Update-Package Syncfusion.Grid.Windows -Version 19.2.0.59```
-4. The NuGet package manager will update the Syncfusion WinForms NuGet package as well as the dependencies it has.
\ No newline at end of file
+4. The NuGet package manager will update the Syncfusion WinForms NuGet package as well as its dependencies. When the update is complete, the console shows the updated package version.
+
+5. After the upgrade, perform a **Clean** and then **Rebuild** of the solution. Verify the upgraded version in the **Installed** tab of the NuGet Package Manager or in the `.csproj`/`.vbproj` file.
\ No newline at end of file
diff --git a/WindowsForms/Visual-Studio-Integration/Add-References.md b/WindowsForms/Visual-Studio-Integration/Add-References.md
index f9329b57d..0ffb6700a 100644
--- a/WindowsForms/Visual-Studio-Integration/Add-References.md
+++ b/WindowsForms/Visual-Studio-Integration/Add-References.md
@@ -1,7 +1,7 @@
---
layout: post
-title: Add a Syncfusion References| WinForms | Syncfusion
-description: Syncfusion Reference Manger extension is add-in to add the Syncfusion references into the WinForms application
+title: Add a Syncfusion Reference | WinForms | Syncfusion
+description: The Syncfusion Reference Manager extension is an add-in that adds the required Syncfusion references to a WinForms application.
platform: windowsforms
control: Syncfusion Extensions
documentation: ug
@@ -19,19 +19,19 @@ Follow the given steps to add the Syncfusion® references in Visual Studio:
1. Open a new or existing **WinForms** application.
-2. To open Syncfusion® Reference Manager Wizard, follow either one of the options below:
+2. To open the Syncfusion® Reference Manager, follow either of the options below:
**Option 1:**
- Click **Extensions->Syncfusion Menu** and choose **Essential Studio® for WinForms > Add References…** or any other Form in **Visual Studio**.
+ Click **Extensions -> Syncfusion Menu** and choose **Essential Studio® for WinForms -> Add References…** or any other Form in **Visual Studio**.
- N> In Visual Studio 2017 or lower, you can see the Syncfusion menu directly in the Visual Studio menu.
+ N> In Visual Studio 2017 or lower, the Syncfusion® menu is available directly in the Visual Studio main menu.
[Syncfusion Reference Manager via Syncfusion Menu](Syncfusion-Reference-Manger_images/Syncfusion_Menu_AddReference.png)
**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.
+ Right-click the selected project file in **Solution Explorer**, then select **Syncfusion® Reference Manager…** from the context menu. The following screenshot shows this option in Visual Studio.
@@ -53,26 +53,18 @@ Follow the given steps to add the Syncfusion® references in Visual Studio:
-
- N> Window Forms (.NET Core 3.1 and .NET 5.0) application in Visual Studio 2019 is supported from 18.2.0.44 version and .NET 6.0 application in Visual Studio 2022 is supported from 19.4.0.38 and .NET 7.0 application in Visual Studio 2022 is supported from 20.4.0.38 and .NET 8.0 application in Visual Studio 2022 is supported from 23.2.4. Version combobox is not visible for nuget option.
-
+ N> Windows Forms (.NET Core 3.1 and .NET 5.0) applications in Visual Studio 2019 are supported from 18.2.0.44. .NET 6.0 applications in Visual Studio 2022 are supported from 19.4.0.38. .NET 7.0 applications in Visual Studio 2022 are supported from 20.4.0.38. .NET 8.0 applications in Visual Studio 2022 are supported from 23.2.4. The Version combobox is not visible for the NuGet option.
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.
+5. Click **OK**. The listed Syncfusion assemblies are added to the project. A notification **"Syncfusion assemblies have been added successfully"** appears in the 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> Syncfusion® provides Reference Manager support for specific .NET Framework versions, based on the assemblies shipped with the Syncfusion® Essential Studio® setup. If you attempt to add Syncfusion® assemblies to a project whose target framework is not supported by the selected Syncfusion® version, a dialog will appear with the following message: **“Current build v{version} does not support this framework v{Framework Version}.”**
-
-
-
-
-
-
+N> Syncfusion® provides Reference Manager support for specific .NET Framework versions, based on the assemblies shipped with the Syncfusion® Essential Studio® setup. If you attempt to add Syncfusion® assemblies to a project whose target framework is not supported by the selected Syncfusion® version, a dialog will appear with the following message: **“Current build v{version} does not support this framework v{Framework Version}.”**
\ No newline at end of file
diff --git a/WindowsForms/Visual-Studio-Integration/Check-for-Updates.md b/WindowsForms/Visual-Studio-Integration/Check-for-Updates.md
index fb3ded4fd..ac3a998ae 100644
--- a/WindowsForms/Visual-Studio-Integration/Check-for-Updates.md
+++ b/WindowsForms/Visual-Studio-Integration/Check-for-Updates.md
@@ -9,21 +9,21 @@ documentation: ug
# Check for Updates in Syncfusion® Essential Windows Forms
-Syncfusion® provides the check for update extensions to find the latest version of the essential release. If it is available, then provide the option to update to the most recent version of the Essential Studio® release. So that you always get the latest features, fixes, and improvements by installing the latest version.
+Syncfusion® provides the Check for Updates extension to find the latest version of the Essential Studio® release. If an update is available, the extension provides the option to update to the most recent version. This ensures you always get the latest features, fixes, and improvements by installing the most recent version.
-I> The Syncfusion® Check for updates is available from v17.1.0.32.
+I> The Syncfusion® Check for Updates feature is available from v17.1.0.32.
-You can check updates availability in Visual Studio, and then install the update version if required.
+You can check for available updates in Visual Studio, and then install the update version if required.
1. Choose **Extensions->Syncfusion -> Check for Updates…** in the Visual Studio menu
- N> In Visual Studio 2017 or lower, you can see the Syncfusion menu directly in the Visual Studio menu.
+ N> In Visual Studio 2017 or lower, the Syncfusion® menu is available directly in the Visual Studio main menu.
-2. When there is an update, **Update** dialog box opens.
+2. The **Check for Updates** dialog opens. If no update is available, the dialog indicates that you are using the latest version. If an update is available, the dialog lists the latest version and provides the **Update** option.
diff --git a/WindowsForms/Visual-Studio-Integration/Item-Template.md b/WindowsForms/Visual-Studio-Integration/Item-Template.md
index dcf7cbaf2..29c1d0b97 100644
--- a/WindowsForms/Visual-Studio-Integration/Item-Template.md
+++ b/WindowsForms/Visual-Studio-Integration/Item-Template.md
@@ -15,39 +15,35 @@ I> The Syncfusion® Windows Forms item templates are available from v13.1.0.21.
The following steps will guide you in adding the Syncfusion® WinForms components to your Visual Studio WinForms application.
-> Check whether the **WinForms Extensions - Syncfusion** are installed or not in Visual Studio Extension Manager by going to **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 or later and Visual Studio 2017 or lower by going to **Tools -> Extensions and Updates -> Installed**. If this extension is not installed, please install the extension by following the steps from the [download and installation](https://help.syncfusion.com/windowsforms/visual-studio-integration/download-and-installation) help topic.
+> Check whether the **Syncfusion WinForms** extension is installed in Visual Studio Extension Manager by going to **Extensions → Manage Extensions → Installed** for Visual Studio 2019 or later, and to **Tools → Extensions and Updates → Installed** for Visual Studio 2017 or lower. If this extension is not installed, install the extension by following the steps from the [download and installation](https://help.syncfusion.com/windowsforms/visual-studio-integration/download-and-installation) help topic.
## Add components using Syncfusion® Item Template
-1. Open a new or existing WinForms application.
+1. Open a new or existing **WinForms** project. Then choose one of the following options to open the wizard:
- **Option 1:**
+ - **Option 1:** In **Solution Explorer**, right-click the WinForms project and choose **Add Syncfusion Item...**.
-2. From the **Solution Explorer, right-click** on the WinForms application. Choose **Add Syncfusion Item...**.
+ 
- 
+ - **Option 2:** Click **Extensions → Essential Studio® for WinForms → Add Syncfusion Item…** in Visual Studio.
- **Option 2:**
+ 
-3. Click **Extensions > Essential Studio® for WinForms > Add Syncfusion Item…** in Visual Studio.
+2. The Syncfusion® WinForms Item Template wizard opens as shown below.
- 
+ 
-4. The Syncfusion® WinForms Item Template wizard will be launched as follows.
+3. Choose one of the following scenarios to add a Syncfusion® form in your application:
- 
+ **Default Form with Syncfusion® Component:** If you select the **Default** form and then choose any Syncfusion® component and the specific features that are essential for your project, the selected component is added with the default Microsoft WinForms layout.
-5. Please choose one of the following scenarios to add Syncfusion Forms in your application:
+ 
- **Default Form with Syncfusion Component:** If you select the **Default** form and then choose any Syncfusion® component and the specific features that are essential for your project, the selected component will be added with the default Microsoft form layout.
+ **Syncfusion® Form with Syncfusion® Component:** If you select a Syncfusion® form and then choose any Syncfusion® component and the specific features that are essential for your project, the selected component is added with the layout of the selected Syncfusion® form.
- 
+ 
- **Syncfusion Form with Syncfusion Component:** If you select a Syncfusion® form and then choose any Syncfusion® component and the specific features that are essential for your project, the selected component will be added with the layout of the selected Syncfusion® form.
-
- 
-
- **Syncfusion Form without Syncfusion Components:** If you select a Syncfusion® form and then choose the **Blank** option from the Syncfusion® component list, a blank Syncfusion® form will be added without any Syncfusion® components.
+ **Syncfusion® Form without Syncfusion® Components:** If you select a Syncfusion® form and then choose **Blank** from the Syncfusion® component list, a blank Syncfusion® form is added without any Syncfusion® components.
diff --git a/WindowsForms/Visual-Studio-Integration/Overview.md b/WindowsForms/Visual-Studio-Integration/Overview.md
index 804638c0e..c4a8d6b7a 100644
--- a/WindowsForms/Visual-Studio-Integration/Overview.md
+++ b/WindowsForms/Visual-Studio-Integration/Overview.md
@@ -17,27 +17,27 @@ N> Syncfusion® Extension is published in Visual Studio Marketplace. We provided
[Visual Studio 2019 or lower](https://marketplace.visualstudio.com/items?itemName=SyncfusionInc.Windows-Extensions).
-I> The Syncfusion® WinForms menu option is available from v17.1.0.32.
+I> The Syncfusion® WinForms menu option is available from v17.1.0.32. The same availability note also applies to the [Check for Updates](https://help.syncfusion.com/windowsforms/visual-studio-integration/check-for-updates) feature.
-The Syncfusion® provides the following supports in Visual Studio:
+Syncfusion® provides the following features in Visual Studio:
-1. [Create Project](https://help.syncfusion.com/windowsforms/Visual-Studio-Integration/Create-Project): Creates the Syncfusion® WinForms application by adding the required Syncfusion® assemblies and forms.
-2. [Item Template](https://help.syncfusion.com/windowsforms/Visual-Studio-Integration/Item-Template): Add predefined Syncfusion® items (Forms) and the required Syncfusion® assemblies in WinForms Application.
-3. [Add References](https://help.syncfusion.com/windowsforms/Visual-Studio-Integration/Add-References): Add the required Syncfusion® assembly to Windows project reference based on the selected control(s).
+1. [Create Project](https://help.syncfusion.com/windowsforms/visual-studio-integration/template-studio): Creates the Syncfusion® WinForms application by adding the required Syncfusion® assemblies and forms.
+2. [Item Template](https://help.syncfusion.com/windowsforms/visual-studio-integration/item-template): Add predefined Syncfusion® items (Forms) and the required Syncfusion® assemblies in WinForms Application.
+3. [Add References](https://help.syncfusion.com/windowsforms/visual-studio-integration/add-references): Add the required Syncfusion® assembly to Windows project reference based on the selected control(s).
4. [Toolbox](https://help.syncfusion.com/windowsforms/visual-studio-integration/toolbox-configuration): Configure the Syncfusion® controls into the Visual Studio .NET toolbox.
-5. [Troubleshooting](https://help.syncfusion.com/windowsforms/Visual-Studio-Integration/Troubleshooting): Troubleshoots the project with the Syncfusion® configuration and apply the fix like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly.
+5. [Troubleshooting](https://help.syncfusion.com/windowsforms/visual-studio-integration/troubleshooting): Troubleshoots the project with the Syncfusion® configuration and apply the fix like, wrong Framework Syncfusion® assembly added to the project or missing any Syncfusion® dependent assembly of a referred assembly.
-**No project selected in Visual Studio**
+**Figure 1: Syncfusion® menu when no project is selected in Visual Studio**
-
+
-**Selected Microsoft WinForms application in Visual Studio**
+**Figure 2: Syncfusion® menu when a Microsoft WinForms application is selected in Visual Studio**
-
+
-**Selected Syncfusion® WinForms application in Visual Studio**
+**Figure 3: Syncfusion® menu when a Syncfusion® WinForms application is selected 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/WindowsForms/Visual-Studio-Integration/Syncfusion-Notifications.md b/WindowsForms/Visual-Studio-Integration/Syncfusion-Notifications.md
index 49873efe6..955c28d4c 100644
--- a/WindowsForms/Visual-Studio-Integration/Syncfusion-Notifications.md
+++ b/WindowsForms/Visual-Studio-Integration/Syncfusion-Notifications.md
@@ -15,11 +15,19 @@ N> The Syncfusion® Notification feature is available from Essential Studio® v2
## Notification Configuration
-The Syncfusion® Options page allows you to configure notification settings. Customise trial and newer version notifications with a simple true or false toggle.
+The Syncfusion® Options page allows you to configure notification settings. Each notification can be toggled **on** (true) or **off** (false). Toggling a notification off suppresses that notification at runtime, while leaving the others active.
-It can be accessed by clicking **Tools -> Options -> Syncfusion -> Winforms**
+To configure a notification:
-
+1. Open Visual Studio.
+2. Navigate to **Tools → Options → Syncfusion → WinForms**.
+3. Locate the notification to disable.
+4. Set its value to **False** to disable the notification or **True** to enable it.
+5. Click **OK**.
+
+The toggles are per-user settings stored in the Visual Studio profile, and they persist across Visual Studio upgrades on the same machine.
+
+
## Notification Types
diff --git a/WindowsForms/Visual-Studio-Integration/Template-Studio.md b/WindowsForms/Visual-Studio-Integration/Template-Studio.md
index 8d7b43380..7ef10fa69 100644
--- a/WindowsForms/Visual-Studio-Integration/Template-Studio.md
+++ b/WindowsForms/Visual-Studio-Integration/Template-Studio.md
@@ -20,9 +20,9 @@ Create the Syncfusion® WinForms project using the Visual Studio Project Templat
> Check whether the **WinForms Extensions - Syncfusion** are installed or not in Visual Studio Extension Manager by going to **Extensions -> Manage Extensions -> Installed** for Visual Studio 2019 or later, and for Visual Studio 2017 by going to **Tools -> Extensions and Updates -> Installed**. If this extension is not installed, please install the extension by following the steps from the [download and installation](https://help.syncfusion.com/windowsforms/visual-studio-integration/download-and-installation) help topic.
-1. Open the Visual Studio 2022.
+1. Open Visual Studio 2017, 2019, or 2022.
-2. Select one of the following options to create the Syncfusion® WinForms application
+2. Select one of the following options to create the Syncfusion® WinForms application:
**Option 1:**
Choose **Extension -> Syncfusion -> Essential Studio® for WinForms -> Create New Syncfusion Project…** from the Visual Studio menu.
@@ -52,17 +52,17 @@ Create the Syncfusion® WinForms project using the Visual Studio Project Templat
- **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.
+ **Predefined template:** Choose this option to select from 5 predefined templates, including Calendar, Contact, Outlook, Docking Manager, and Spreadsheet. You can create your application without further steps.
- **Project type:** Choose this option to select from 4 project types, including Blank, Menu Bar, Ribbon, and Tabbed Form.
+ **Project type:** Choose this option to select from 4 project types, including Blank, Menu Bar, Ribbon, and Tabbed Form. Blank creates an empty project, Menu Bar creates a project with a top menu bar, Ribbon creates a project with a ribbon, and Tabbed Form creates a project with a tabbed MDI layout.
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.
+ To unselect an added control, click the X icon next to the corresponding control in the **Project Details** list.
N> The Control Features option is not accessible for Blank Pages.
@@ -74,8 +74,8 @@ Create the Syncfusion® WinForms project using the Visual Studio Project Templat
- N> The App Features option is not accessible for .NET Framework.
-
+ N> The App Features option is not accessible for .NET Framework.
+
**Project Details Section**
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.
@@ -88,6 +88,8 @@ Create the Syncfusion® WinForms project using the Visual Studio Project Templat
+ N> After the project is created, open the **Package Manager Console** or the **NuGet Package Manager** and confirm that all Syncfusion® packages restored successfully. If any package shows a warning, run **Update-Package -reinstall** for that package.
+
To find out which NuGet packages are needed for other WinForms controls, please refer to this [documentation link](https://help.syncfusion.com/windowsforms/control-dependencies) for detailed information on the required packages for each control.
10. When you create a WinForms project, the following Dependency Injection (DI) setup is added to the **Program.cs** file. This setup registers services, view models, and views with the DI container, ensuring proper functionality and service management within your application. The **ConfigureServices** method in the **Program.cs** file establishes this DI setup by managing the application’s services, view models, and views. Here’s a detailed breakdown:
@@ -125,7 +127,7 @@ Here's a simple explanation:
- > The .NET 8.0 and .NET 9.0 options will be available in the Select a framework version dropdown only if the respective .NET SDKs are installed on your system. The table below outlines the .NET versions, the specific product versions from which they are available, and the Visual Studio versions that support them:
+ > The .NET 8.0, .NET 9.0, and .NET 10.0 options are available in the **Select a framework version** dropdown only if the respective .NET SDKs are installed on the system. The table below outlines the .NET versions, the product versions from which they are available, and the Visual Studio versions that support them:
>
>
>
@@ -145,6 +147,11 @@ Here's a simple explanation:
> | v27.2.2 |
> Visual Studio 2022 |
>
+ >
+ > | .NET 10.0 |
+ > v28.1.6 |
+ > Visual Studio 2022 |
+ >
>
>
diff --git a/WindowsForms/Visual-Studio-Integration/Toolbox-Configuration.md b/WindowsForms/Visual-Studio-Integration/Toolbox-Configuration.md
index b22820652..e3ac7a30e 100644
--- a/WindowsForms/Visual-Studio-Integration/Toolbox-Configuration.md
+++ b/WindowsForms/Visual-Studio-Integration/Toolbox-Configuration.md
@@ -17,7 +17,9 @@ Syncfusion® controls will be automatically configured in the Visual
Use the following steps to add the Syncfusion® WinForms controls through the Syncfusion® Toolbox Installer:
-1. To launch Toolbox configuration utility, follow either one of the options below:
+N> The Syncfusion® Essential Studio® WinForms installer must be installed before running the Toolbox Installer. If multiple Visual Studio versions are installed on the same machine, run the Toolbox Installer once and select each Visual Studio version to configure.
+
+1. To launch the Toolbox Configuration utility, follow either of the options below:
**Option 1:**
To open the Syncfusion Control Panel, click **Add On and Utilities > Toolbox Installer**.
@@ -45,7 +47,7 @@ Use the following steps to add the Syncfusion® WinForms controls through the Sy
N> You can also configure Syncfusion® controls from a lower version Framework assembly to higher version of Visual Studio.
-3. The successful configuration of Toolbox is indicated by an Information message. Click **OK**.
+3. The successful configuration of the Toolbox is indicated by an information message. Click **OK**.
diff --git a/WindowsForms/Visual-Studio-Integration/Troubleshooting.md b/WindowsForms/Visual-Studio-Integration/Troubleshooting.md
index b1520934e..8464e1b6c 100644
--- a/WindowsForms/Visual-Studio-Integration/Troubleshooting.md
+++ b/WindowsForms/Visual-Studio-Integration/Troubleshooting.md
@@ -9,10 +9,10 @@ documentation: ug
# Troubleshoot the project
-Troubleshoot your project for Syncfusion® configuration issues and apply necessary fixes, such as adding a Syncfusion® assembly targeting the incorrect .NET Framework version or resolving missing dependent Syncfusion® assemblies. The Syncfusion Troubleshooter is capable of performing the following tasks:
+Troubleshoot your project for Syncfusion® configuration issues. Apply fixes such as adding a Syncfusion® assembly that targets the correct .NET Framework version, or resolving missing dependent Syncfusion® assemblies. The Syncfusion® Troubleshooter performs the following tasks:
-* Report the Configuration issues.
+* Report the configuration issues.
* Apply the solution.
## Report the Configuration issues
diff --git a/WindowsForms/Visual-Studio-Integration/download-and-installation.md b/WindowsForms/Visual-Studio-Integration/download-and-installation.md
index 935a187ad..c7cb1bf20 100644
--- a/WindowsForms/Visual-Studio-Integration/download-and-installation.md
+++ b/WindowsForms/Visual-Studio-Integration/download-and-installation.md
@@ -1,6 +1,6 @@
---
layout: post
-title: Downloand and Installation | WinForms | Syncfusion
+title: Download and Installation | WinForms | Syncfusion
description: this section provide the information about how to download and install the extensions in Visual Studio.
platform: windowsforms
control: Syncfusion Extensions
@@ -19,7 +19,7 @@ Syncfusion® publishes its Visual Studio extension on the Visual Stud
The following software prerequisites must be installed to use the Syncfusion® WinForms extension for creating projects, adding code snippets, converting, and upgrading Syncfusion® WinForms applications.
-* [Visual Studio 2010 or later](https://visualstudio.microsoft.com/downloads).
+* [Visual Studio 2015 or later](https://visualstudio.microsoft.com/downloads).
## Install through the Visual Studio Manage Extensions
diff --git a/WindowsForms/ai-tools/ai-powered-development.md b/WindowsForms/ai-tools/ai-powered-development.md
index 3973bf79b..7591f1e91 100644
--- a/WindowsForms/ai-tools/ai-powered-development.md
+++ b/WindowsForms/ai-tools/ai-powered-development.md
@@ -100,7 +100,6 @@ Choose one of these two options:
The MCP Server establishes a direct connection between your IDE-integrated AI and Syncfusion WinForms documentation, enabling the AI to retrieve real-time information for unfamiliar controls. Using Retrieval-Augmented Generation (RAG), it injects relevant documentation into the AI's context to generate accurate and up-to-date code suggestions.
-
**What you get:**
- Complete documentation for all 145+ WinForms controls
- Live API references (properties, methods, events)
@@ -190,7 +189,7 @@ public partial class EmployeeForm : Form
InitializeComponent();
SetupGrid();
}
-
+
private void SetupGrid()
{
employeeGrid = new GridControl();
@@ -213,7 +212,7 @@ public partial class EmployeeForm : Form
this.Controls.Add(employeeGrid);
LoadEmployees();
}
-
+
private void LoadEmployees()
{
// Load employee data
@@ -249,7 +248,6 @@ If you encounter unexpected results, use this as a quick diagnostic reference:
| Data binding not working | Incorrect binding setup or DataSource not assigned | Set DataSource property correctly; use WinForms binding patterns with GridControl and other bound controls |
| NuGet package conflicts | Multiple incompatible Syncfusion versions installed | Use matching Syncfusion versions for all components in your project |
-
## Quick Reference
| If you want... | Do this... |
diff --git a/WindowsForms/arm-support.md b/WindowsForms/arm-support.md
index 2a3e02dd5..91e6f7a80 100644
--- a/WindowsForms/arm-support.md
+++ b/WindowsForms/arm-support.md
@@ -9,7 +9,7 @@ documentation: ug
# ARM support in Windows Forms Controls
-The Syncfusion WinForms components are compatible with ARM64 devices. You can build the application with our components. The following components/features are alone yet to be supported for ARM64 device compatibility. Based on the feasibility, we will provide the support for the below components/features soon,
+The Syncfusion WinForms components are compatible with ARM64 devices. You can build the application with our components. The following components/features are not yet supported for ARM64 device compatibility. Based on the feasibility, we will provide support for the below components/features soon,
* PDF library: HTML to PDF conversion
* PDF library: OCR Processing
diff --git a/WindowsForms/dotnet-core-compatibility.md b/WindowsForms/dotnet-core-compatibility.md
index 0238ee74e..607db2ce7 100644
--- a/WindowsForms/dotnet-core-compatibility.md
+++ b/WindowsForms/dotnet-core-compatibility.md
@@ -7,15 +7,15 @@ control: .NET Core
documentation: ug
---
-# WinForms Applications using .NET Core and Syncfusion® WinForms Controls
+# Using Syncfusion WinForms with .NET Core
-Syncfusion® Essential Studio® for Windows Forms suits .NET core assemblies for building Windows Forms .NET Core applications using Syncfusion® Controls. This section explains how to create the project in .NET Core application and using Syncfusion® Windows Forms controls.
+Syncfusion® Essential Studio® for Windows Forms provides .NET Core assemblies for building Windows Forms .NET Core applications using Syncfusion® Controls. This section explains how to create the project in a .NET Core application and using Syncfusion® Windows Forms controls.
-N> All Syncfusion® Windows Forms controls supports .NET Core Framework except the controls labeled as `classic`.
+N> All Syncfusion® Windows Forms controls support .NET Core Framework except the controls labeled as `classic`.
## Create a .NET Core project
-**Step 1**: Open Visual Studio, go to **File > New > Project...** and you can now see **Create a new project** dialog. Here, select **Windows Forms App (.NET Core)** template and click **Next**.
+**Step 1**: Open Visual Studio, go to **File > New > Project...** and the following **Create a new project** dialog appears. Here, select **Windows Forms App (.NET Core)** template and click **Next**.
@@ -25,7 +25,7 @@ N> All Syncfusion® Windows Forms controls supports .NET Core Framewo
**Step 3**: In the Additional information window, select .NET 6.0 (Long-term support) for the Framework setting, and then click **Create**.
-
+
**Step 4**: Finally, Windows Forms (.NET Core) sample project is created.
@@ -67,8 +67,8 @@ We are now going to see a demo on how to add **ButtonAdv** control in WinForms .
{% highlight c# %}
ButtonAdv button = new ButtonAdv();
-button.Text = ”ButtonAdv”;
-this.controls.add(button);
+button.Text = "ButtonAdv";
+this.Controls.Add(button);
{% endhighlight %}
{% endtabs %}
diff --git a/WindowsForms/dotnet-core-designtime-feature.md b/WindowsForms/dotnet-core-designtime-feature.md
index 3645ae3f3..228ff5f1b 100644
--- a/WindowsForms/dotnet-core-designtime-feature.md
+++ b/WindowsForms/dotnet-core-designtime-feature.md
@@ -11,7 +11,7 @@ documentation: ug
## Overview
-We have expanded design-time support—such as Smart Tags, Custom Collection Editors, and Custom Forms for UITypeEditor—to include controls targeting .NET 6 and higher, which were previously available only in the .NET Framework.
+We have added design-time support—such as Smart Tags, Custom Collection Editors, and Custom Forms for UITypeEditor—to include controls targeting .NET 6 and higher, which were previously available only in the .NET Framework.
## Why We Use the WinForms Designer SDK
Microsoft has introduced the **WinForms Designer SDK** NuGet package to support custom design-time experiences in Visual Studio for .NET Core and later versions. This SDK replaces the traditional designer APIs that were previously part of the .NET Framework and Windows OS.
@@ -22,11 +22,11 @@ The new Designer SDK offers several key advantages:
* Not reliant on the .NET Framework
* Fully integrated with Visual Studio
-It provides essential extension points and base classes that allow developers to implement advanced design-time features such as, **Smart Tags, Custom Collection Editors, Custom Forms for UITypeEditor**.
+It provides essential extension points and base classes that allow developers to implement advanced design-time features such as **Smart Tags, Custom Collection Editors, Custom Forms for UITypeEditor**.
These features are now available for controls targeting .NET 6 and higher.
-To enable this functionality, we have included the **WinForms Designer SDK** as a dependency in our control NuGet packages starting from this version **v26.1.35**. This ensures a consistent and enhanced design-time experience across modern .NET platforms.
+To enable this functionality, we have added the **WinForms Designer SDK** as a dependency in our control NuGet packages starting from this version **v26.1.35**. This ensures a consistent and enhanced design-time experience across modern .NET platforms, including .NET 6, .NET 7, .NET 8, .NET 9, and later.
## Control Package Details
We have added the **WinForms Designer SDK** as a dependency in the following control packages. Please refer to the table below for details:
@@ -145,6 +145,6 @@ N> The listed package assemblies are built against the Designer SDK to provide i
Certain controls properties in .NET Core WinForms have known design‑time limitations. These issues are largely caused by the out‑of‑process WinForms Designer architecture, which results in UITypeEditors, collection editors, and smart tags having only limited communication with the design surface.
-We have documented these details in the following Knowledge Base article. Please refer to it for comprehensive information.
+We have documented these details in the following Knowledge Base article. Please refer to it for comprehensive information. Refer to the [Visual Studio version requirements](https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes) for the .NET 6 and later WinForms Designer SDK support.
**KB Link** : [Known Design-Time Limitations in .NET Core WinForms and Syncfusion Controls](https://support.syncfusion.com/kb/article/22154/known-design-time-limitations-in-net-core-winforms-and-syncfusion-controls)
diff --git a/WindowsForms/dotnet-framework-compatibility.md b/WindowsForms/dotnet-framework-compatibility.md
index 9e58bd47d..50a6d24af 100644
--- a/WindowsForms/dotnet-framework-compatibility.md
+++ b/WindowsForms/dotnet-framework-compatibility.md
@@ -9,11 +9,11 @@ documentation: ug
# .NET Framework and .NET Core Compatibility
-Syncfusion® Windows Forms Controls are always compatible latest .NET Framework and .NET Core versions.
+Syncfusion® Windows Forms Controls are always compatible with the latest .NET Framework and .NET Core versions.
## Version Compatibility
-Below table represents the supported Syncfusion® Essential Studio® version for .NET Framework and .NET Core versions.
+The following table summarizes the supported Syncfusion® Essential Studio® versions for .NET Framework and .NET Core versions.
diff --git a/WindowsForms/right-to-left.md b/WindowsForms/right-to-left.md
index a7645d577..4b7d811d5 100644
--- a/WindowsForms/right-to-left.md
+++ b/WindowsForms/right-to-left.md
@@ -9,6 +9,6 @@ documentation: ug
# Right to Left support in Syncfusion Windows Forms Controls
-Right to Left (RTL) support displays the content from right-to-left direction by setting the [RightToLeft](https://learn.microsoft.com/en-us/dotnet/api/system.windows.forms.control.righttoleft?redirectedfrom=MSDN&view=netframework-4.8#System_Windows_Forms_Control_RightToLeft) property to `Yes`. This is helpful to support the Right-to-Left scripted languages like Arabic, Hebrew, Urdu, etc.,
+Right to Left (RTL) support displays the content from right-to-left direction by setting the [RightToLeft](https://learn.microsoft.com/en-us/dotnet/api/system.windows.forms.control.righttoleft?redirectedfrom=MSDN&view=netframework-4.8#System_Windows_Forms_Control_RightToLeft) property to `Yes`. This is useful for supporting the Right-to-Left scripted languages like Arabic, Hebrew, Urdu, etc.
-All Windows Forms Syncfusion controls supports Right-to-Left (RTL) based on FlowDirection property. In addition to that, all controls provides [localization](https://help.syncfusion.com/windowsforms/localization) support to change language of strings used in control specific to any culture.
+All Windows Forms Syncfusion controls support Right-to-Left (RTL). In addition to that, all controls provide [localization](https://help.syncfusion.com/windowsforms/localization) support to change the language of strings used in a control specific to any culture.
\ No newline at end of file
diff --git a/WindowsForms/skills/component-skills.md b/WindowsForms/skills/component-skills.md
index b4fba710d..b62bffa66 100644
--- a/WindowsForms/skills/component-skills.md
+++ b/WindowsForms/skills/component-skills.md
@@ -10,7 +10,7 @@ domainurl: ##DomainURL##
# Syncfusion Windows Forms Agent Skills for AI Assistants
-This guide introduces **Syncfusion Windows Forms Skills**, a knowledge package that enables AI assistants (VS Code, Cursor, CodeStudio, etc.) to understand and generate accurate Windows Forms code using official APIs, patterns, and theming guidelines.
+This guide introduces **Syncfusion Windows Forms Skills**, a knowledge package that enables AI assistants (Visual Studio Code, Cursor, CodeStudio, etc.) to understand and generate accurate Windows Forms code using official APIs, patterns, and theming guidelines.
These skills eliminate common issues with generic AI suggestions by grounding the assistant in accurate component usage patterns, API structures, supported features, and project‑specific configuration.
@@ -20,7 +20,7 @@ Before installing Syncfusion® Windows Forms
- Required [Node.js](https://nodejs.org/en/) version >= 16
- Windows Forms application (existing or new); see [Overview](https://help.syncfusion.com/windowsforms/overview)
-- A supported AI agent or IDE that integrates with the Skills CLI (VS Code, Syncfusion® Code Studio, Cursor, etc.)
+- A supported AI agent or IDE that integrates with the Skills CLI (Visual Studio Code, Syncfusion® Code Studio, Cursor, etc.)
## Key Benefits
@@ -37,7 +37,7 @@ Before installing Syncfusion® Windows Forms
**Design‑System Guidance**
- Theme usage, including light and dark variants
-- VisualStyle patterns and customization approaches
+- [VisualStyle](https://help.syncfusion.com/windowsforms/visualstyle) patterns and customization approaches
- Consistent design alignment across Syncfusion® Windows Forms components
## Installation
@@ -68,8 +68,7 @@ npx skills add syncfusion/winforms-ui-components-skills
{% endhighlight %}
{% endtabs %}
-The terminal will display a list of available skills. Use the arrow keys to navigate, the space bar to select the desired skills, and the Enter key to confirm.
-{% tabs %}
+The terminal will display a list of available skills. Use the **arrow keys** to move between skills, the **space bar** to toggle a skill on or off, and the **Enter** key to confirm.
{% highlight bash tabtitle="CMD" %}
Select skills to install (space to toggle)
@@ -125,7 +124,7 @@ Choose your installation scope (project-level or global), then confirm to comple
{% endhighlight %}
{% endtabs %}
-This registers the Syncfusion® skill pack so your AI assistant can automatically load it in supported IDEs such as [Code Studio](https://help.syncfusion.com/code-studio/reference/configure-properties/skills), [Visual Studio Code](https://code.visualstudio.com/docs/copilot/customization/agent-skills), and [Cursor](https://cursor.com/docs/skills).
+This registers the Syncfusion® skill pack so your AI assistant can automatically load it in supported IDEs such as [Code Studio](https://help.syncfusion.com/code-studio/reference/configure-properties/skills), [Visual Studio Code](https://code.visualstudio.com/docs/copilot/customization/agent-skills), and [Cursor](https://cursor.com/docs/skills). After installation, restart your IDE (or use the **Reload Window** command) so the IDE can detect the newly added skill files.
To learn more about the Skills CLI, refer [here](https://www.skills.sh/docs).
@@ -144,7 +143,7 @@ To learn more about the Skills CLI, refer [here](https://www.skills.sh/docs).
Once skills are installed, the assistant can be used to generate and update Syncfusion® Windows Forms code for tasks such as:
- "Add a DataGrid with paging, sorting, and filtering."
-- "Create a Scheduler with week view and drag‑drop."
+- "Create a Schedule control with week view and drag‑drop."
## Skills CLI Commands
@@ -212,9 +211,10 @@ Yes. Once installed, supported agents automatically detect and load relevant ski
**Skills are not being loaded**
-Verify that skills are installed in the correct agent directory, restart the IDE, and confirm that the agent supports external skill files.
+Verify that skills are installed in the correct agent directory (for example, `.agents/skills/`), confirm with `npx skills list`, restart the IDE (or run the **Reload Window** command), and confirm that the agent supports external skill files.
## See also
- [Agent Skills Standards](https://agentskills.io/home)
-- [Skills CLI](https://www.skills.sh/docs)
\ No newline at end of file
+- [Skills CLI](https://www.skills.sh/docs)
+- [VisualStyle](https://help.syncfusion.com/windowsforms/visualstyle)
\ No newline at end of file
diff --git a/WindowsForms/skills/ui-builder-skill.md b/WindowsForms/skills/ui-builder-skill.md
index 3e2fdba36..bdeca9bc2 100644
--- a/WindowsForms/skills/ui-builder-skill.md
+++ b/WindowsForms/skills/ui-builder-skill.md
@@ -136,7 +136,7 @@ Key enforcement points:
After installing Windows Forms UI Builder with APM, the relevant agent and skill files are added to your project under:
-- `.agent/skills/` (skill files)
+- `.agents/skills/` (skill files)
- `.github/agents/` (Windows Forms UI builder agent configuration, based on the selected target)
To start using the skill:
@@ -159,7 +159,7 @@ Create a CMS Admin Dashboard UI featuring a collapsible TreeView in a left panel
{% endpromptcard %}
{% endpromptcards %}
-Generated code follows Windows Forms best practices with proper control layout, event handling, data bindings, strong C# typing, and built-in security measures such as input validation and avoidance of hardcore secrets. The code is fully compatible with Visual Studio designer and Windows Forms conventions.
+Generated code follows Windows Forms best practices with proper control layout, event handling, data bindings, strong C# typing, and built-in security measures such as input validation and avoidance of hard-coded secrets. The code is fully compatible with Visual Studio designer and Windows Forms conventions.
## Best Practices
@@ -173,7 +173,7 @@ Follow these guidelines to get the most out of UI Builder and ensure high-qualit
## Troubleshooting
-- **APM installation failure**: Refer to this [documentation](https://microsoft.github.io/apm/getting-started/installation/#troubleshooting)
+- **APM installation failure**: Refer to this [documentation](https://microsoft.github.io/apm/getting-started/installation/#troubleshooting).
- **Skills not loading**: Ensure the **.agent/** and **.github/agents/** folders exist in your project and that the skill was installed successfully using APM. Verify that the correct agent is selected from the Agent dropdown in your IDE.
@@ -194,9 +194,12 @@ Yes. Supported agents automatically load relevant skills based on your query.
Yes — the generated Windows Forms controls include clear integration points for style adjustments.
**Does it modify files automatically?**
-The skill proposes changes and requires confirmation for insertion; automatic dependency installation may be offered depending on agent permissions.
+The skill proposes changes and requires confirmation for insertion. Automatic dependency installation may be offered depending on agent permissions
## See also
- [Agent Skills Standards](https://agentskills.io/home)
- [Agent Package Manager](https://microsoft.github.io/apm/getting-started/quick-start/)
+- [Theme Studio](https://help.syncfusion.com/windowsforms/skinmanager/theme-studio)
+- [VisualStyle](https://help.syncfusion.com/windowsforms/visualstyle)
+- [Licensing](https://help.syncfusion.com/windowsforms/licensing)
diff --git a/WindowsForms/skins/Getting-Started.md b/WindowsForms/skins/Getting-Started.md
index dc69e2a4b..4d983221f 100644
--- a/WindowsForms/skins/Getting-Started.md
+++ b/WindowsForms/skins/Getting-Started.md
@@ -13,7 +13,7 @@ This section briefly describes how to create a new Windows Forms project in Visu
## Assembly deployment and theme assemblies
-SkinManager presents in the `Syncfusion.Shared.Base` assembly.
+SkinManager is present in the `Syncfusion.Shared.Base` assembly.
@@ -74,13 +74,17 @@ SkinManager.LoadAssembly(GetType(Syncfusion.WinForms.Themes.Office2016Theme).Ass
{% endtabs %}
-## Adding skin manager component
+## Adding SkinManager component
## Through designer
-1) Create a new Windows Forms application in Visual Studio.
+1 Create a new Windows Forms application in Visual Studio.
-2) The `SkinManager` component can be added to designer by dragging it from the toolbox to the design view.
+2) Open the target form in the designer.
+
+3) Drag the `SkinManager` component from the toolbox and drop it onto the designer.
+
+4) Select the `SkinManager` component and use the `Controls` property in the Properties window to choose the control or form to which the theme should be applied.
The following dependent assemblies will be added automatically:
@@ -98,13 +102,13 @@ N> SkinManager does not support the custom themes ( themes generated using Theme
### Applying theme to the form
-Skin manager supports to apply theme for all the control in the form or a container by applying theme to the form or container. So, you do not need to apply theme for each control.
+SkinManager supports applying a theme for all controls in the form or a container by applying the theme to the form or container. So, you do not need to apply the theme for each control.
## Through code
-Theme for a control or form can be applied by settings `Controls` property of `SkinManager`.
+Theme for a control or form can be applied by setting the `Controls` property of `SkinManager`.
{% tabs %}
@@ -132,7 +136,7 @@ skinManager1.Controls = treeViewAdv1
### Applying theme to the form
-Skin manager supports to apply theme for all the control in the form or a container by applying theme to the form or container. So, you do not need to apply theme for each control.
+SkinManager supports applying a theme for all controls in the form or a container by applying the theme to the form or container. So, you do not need to apply the theme for each control.
{% tabs %}
@@ -156,27 +160,27 @@ skinManager1.VisualTheme = VisualTheme.Office2016Black
## Apply Themes to entire application
-Skin manager allows to apply theme for all the controls and forms in an application by setting the [ApplicationVisualTheme](https://help.syncfusion.com/cr/windowsforms/Syncfusion.Windows.Forms.SkinManager.html#Syncfusion_Windows_Forms_SkinManager_ApplicationVisualTheme) property. It allows you to theme entire application using single `ApplicationVisualTheme` property.
+SkinManager allows you to apply a theme to all controls and forms in an application by setting the [ApplicationVisualTheme](https://help.syncfusion.com/cr/windowsforms/Syncfusion.Windows.Forms.SkinManager.html#Syncfusion_Windows_Forms_SkinManager_ApplicationVisualTheme) property. It allows you to theme the entire application using a single `ApplicationVisualTheme` property.
{% tabs %}
{% highlight c# %}
static void Main()
{
- SkinManager.ApplicationVisualTheme = "Office2019Colourful";
+ SkinManager.ApplicationVisualTheme = "Office2019Colorful";
Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(false);
Application.Run(new Form1());
}
-{% endhighlight c# %}
+{% endhighlight %}
{% endtabs %}
-N> Set the `ApplicationVisualTheme` property before main form is initialized.
+N> Set the `ApplicationVisualTheme` property before the main form is initialized.
## Apply theme for individual control
-Theme can be applied to individual component using skin manager or by setting the `ThemeName` property. You need to call the [LoadAssembly](https://help.syncfusion.com/cr/windowsforms/Syncfusion.Windows.Forms.SkinManager.html#Syncfusion_Windows_Forms_SkinManager_LoadAssembly_System_Reflection_Assembly_) method for required themes when applying using the `ThemeName` property also.
+Theme can be applied to an individual control using SkinManager or by setting the `ThemeName` property. You need to call the [LoadAssembly](https://help.syncfusion.com/cr/windowsforms/Syncfusion.Windows.Forms.SkinManager.html#Syncfusion_Windows_Forms_SkinManager_LoadAssembly_System_Reflection_Assembly_) method for required themes when applying using the `ThemeName` property also.
{% tabs %}
@@ -198,13 +202,15 @@ Me.treeViewAdv1.ThemeName = "Office2019Colorful"
## Theme studio based themes
-The Office2019Colorful and HighContrastBlack themes can be customized using the WinForms theme studio. Refer to the theme studio documentation to know how to create custom themes.
+The Office2019Colorful and HighContrastBlack themes can be customized using the WinForms Theme Studio. Refer to the Theme Studio documentation to know how to create custom themes.
+
+Use `Office2019Colorful` for a colorful, modern look and `HighContrastBlack` for high-contrast accessibility scenarios.
-N> Appearance customization settings done in control level will not take effect when theme studio based theme is applied. So, for customization, refer to the Style section.
+N> Appearance customization settings done at the control level will not take effect when a Theme Studio based theme is applied. So, for customization, refer to the Style section.
### Change font for entire application
-When using theme studio based themes, the font for entire application can be customized by setting the [CanOverrideFontFamily](https://help.syncfusion.com/cr/windowsforms/Syncfusion.WinForms.Theme.FontHelper.html#Syncfusion_WinForms_Theme_FontHelper_CanOverrideFontFamily) property to true. This property is used only in constructor.
+When using Theme Studio based themes, the font for the entire application can be customized by setting the [CanOverrideFontFamily](https://help.syncfusion.com/cr/windowsforms/Syncfusion.WinForms.Theme.FontHelper.html#Syncfusion_WinForms_Theme_FontHelper_CanOverrideFontFamily) property to true. This property is used only in a constructor.
{% tabs %}
@@ -228,11 +234,11 @@ FontHelper.FontFamily = New FontFamily("Algerian")
### Styles
-When using theme studio based themes, the appearance for each control or component can be customized using the `ThemeStyle` property.
+When using Theme Studio based themes, the appearance for each control or component can be customized using the `ThemeStyle` property.
N> If the control name starts with **Sf**, you can access appearance properties using the `Style` property, and for the remaining controls, use the `ThemeStyle` property.
-For example, in the following code, different style of each control has been changed.
+For example, in the following code, the style of each control has been changed.
{% tabs %}
@@ -262,9 +268,9 @@ Me.treeViewAdv1.ThemeStyle.TreeNodeAdvStyle.TextColor = System.Drawing.Color.Red
### Overriding user customization when applying theme
-You can customize the appearance of control using the `Style` or `ThemeStyle` property when using theme studio based themes. Syncfusion control provides option whether theme can override style settings using the `CanOverrideStyle` property.
+You can customize the appearance of a control using the `Style` or `ThemeStyle` property when using Theme Studio based themes. The Syncfusion control provides an option for whether the theme can override style settings using the `CanOverrideStyle` property.
-For example, in the following code, TreeView fore color is customized, and theme is applied after that line. If you run the application, theme will not override the fore color settings since the default value of `CanOverrideStyle` is `false`. If you set the `CanOverrideStyle` property to `true` before setting the theme, then fore color setting will be overridden by theme.
+For example, in the following code, the TreeView foreground color is customized, and the theme is applied after that line. If you run the application, the theme will not override the foreground color settings since the default value of `CanOverrideStyle` is `false`. If you set the `CanOverrideStyle` property to `true` before setting the theme, then the foreground color setting will be overridden by the theme.
{% tabs %}
@@ -286,4 +292,4 @@ Me.treeViewAdv1.ThemeStyle.TreeNodeAdvStyle.TextColor = System.Drawing.Color.Red
{% endtabs %}
-
+
\ No newline at end of file
diff --git a/WindowsForms/skins/Overview.md b/WindowsForms/skins/Overview.md
index 03468570c..d88bdf53d 100644
--- a/WindowsForms/skins/Overview.md
+++ b/WindowsForms/skins/Overview.md
@@ -24,9 +24,9 @@ This feature enables you to easily apply uniform style for all the child control
## IT scenarios
-When you create an application with multiple controls, you can apply uniform color for the entire form using this feature.
+When you create an application with multiple Syncfusion controls, you can apply a uniform color for the entire form using the SkinManager component.
-Properties and Methods Tables for Skin Manager
+## Properties and Methods Tables for Skin Manager
### Properties
@@ -73,4 +73,4 @@ Overloads: 1) (Control, String) 2) (Control,VisualTheme) |
NA |
Void |
NA |
-
+
\ No newline at end of file
diff --git a/WindowsForms/theme-studio/theme-studio.md b/WindowsForms/theme-studio/theme-studio.md
index ed7494c48..11e73b005 100644
--- a/WindowsForms/theme-studio/theme-studio.md
+++ b/WindowsForms/theme-studio/theme-studio.md
@@ -9,79 +9,81 @@ documentation: ug
# Getting Started With Windows Forms Theme Studio
-Theme Studio for WinForms can be used to create and apply new theme for Syncfusion® controls from an existing theme. The primary goal here is to deliver an appearance rich Syncfusion® controls that suits bests for every user application, based on their needs.
+Theme Studio for WinForms can be used to create and apply a new theme for Syncfusion® controls from an existing theme. The primary goal here is to deliver appearance-rich Syncfusion® controls that best suit every user application, based on the application's needs.
-## Customizing theme color from theme studio
+## Customizing Theme Color in Theme Studio
-In theme studio utility, each theme has a unique common variable list. When user change the common variable color code value, it will reflect in all the Syncfusion® WinForms controls. All Syncfusion® WinForms control styles are derived from these theme-based common variables. This common variable list is handled inside the theme studio application for customizing theme-based colors.
+In the Theme Studio utility, each theme has a unique common variable list. When the user changes a common variable's color code value, it will reflect in all the Syncfusion® WinForms controls. All Syncfusion® WinForms control styles are derived from these theme-based common variables.
-Let us now see the step-by-step procedure to launch and work with the theme studio utility below.
+The following steps describe how to launch and work with the Theme Studio utility.
**Step 1:**
-On installing the "Syncfusion® Windows Forms" suite, launch and select "Theme Studio" from the start-up panel.
+After installing the "Syncfusion® Windows Forms" suite, launch and select "Theme Studio" from the start-up panel.
**Step 2:**
-The theme studio application form has been divided into two sections: the controls preview section on the right, and the theme customization section on the left.
+The Theme Studio window is divided into two sections: a controls preview on the right and a theme-customization panel on the left.
**Step 3:**
-Click the color pickers in the theme customization section to select the desired color.
+Click a color picker in the theme-customization section to select a color.
**Step 4:**
-The Syncfusion® WinForms controls will be rendered with the newly selected colors in the preview section, after selecting the desired color.
+The Syncfusion® WinForms controls render with the newly selected colors in the preview section.
-## Export the customized theme
+## Export the Customized Theme
You can export the custom theme after changing the theme colors.
**Step 1:**
-Click the Export button in the bottom left corner of the theme studio application.
+Click the Export button in the bottom left corner of the Theme Studio application.
**Step 2:**
-Now the export dialog appears with an option to select either entire controls or just the desired control(s). This option is useful when you have integrated a selective list of Syncfusion® WinForms controls in your application. The theme studio will filter only the selected controls and customize the final output for those controls alone thereby reducing the final output assembly size.
+Now the export dialog appears with an option to select either all controls or just the desired control(s). This option is useful when you have integrated a selective list of Syncfusion® WinForms controls in your application. The Theme Studio will filter only the selected controls and customize the final output for those controls alone, thereby reducing the final output assembly size.
**Step 3:**
-The download theme will come as an assembly (*.dll) file that contains color codes for the selected Syncfusion® WinForms controls.
+The exported theme is delivered as an assembly (*.dll) file that contains color codes for the selected Syncfusion® WinForms controls.
-N> You can enter the assembly name of your own choice while exporting. But remember that the assembly (*.dll) name will be custom theme name, when you refer it in your WinForms application.
+**Note:** You can enter the assembly name of your own choice while exporting. But remember that the assembly (*.dll) name will be the custom theme name, when you refer to it in your WinForms application.
-## Using customized theme in a Windows Forms application
+## Using the Customized Theme in a Windows Forms Application
-You can now add the exported assembly in your Windows Forms application and set the custom theme to the appropriate controls. In this illustration, we are going to witness the custom theme set for SfDataGrid.
+You can now add the exported assembly to your Windows Forms application and set the custom theme to the appropriate controls. In the following example, the custom theme is applied to the SfDataGrid control.
**Step 1:**
-Attach the exported assembly (*.dll) in your Windows Forms project.
+Add the exported assembly (*.dll) as a reference in your Windows Forms project (for example, right-click the project in **Solution Explorer** and choose **Add** → **Reference** → **Browse**, select the exported assembly file).
+
+**Note:** Close Theme Studio before referencing the exported assembly file to avoid file locking errors.
@@ -90,7 +92,8 @@ Attach the exported assembly (*.dll) in your Windows Forms project.
Load the Theme assembly in Program.cs of your application and the initialize a SfDataGrid control in the main form and set it’s "ThemeName" property exactly to the assembly name.
{% tabs %}
-{% highlight c# %}
+
+{% highlight C# %}
static class Program
{
@@ -100,24 +103,26 @@ Load the Theme assembly in Program.cs of your application and the initialize a S
[STAThread]
static void Main()
{
- Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense(DemoCommon.FindLicenseKey());
+ Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense(DemoCommon.FindLicenseKey());
SkinManager.LoadAssembly(typeof(VioletTheme).Assembly);
Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(false);
Application.Run(new Form1());
}
}
-
+
sfDataGrid1.ThemeName = "VioletTheme";
-
+
{% endhighlight %}
-{% highlight vb %}
+
+{% highlight VB %}
Module Program
- Private Sub Main()
+ Private Sub Main()
Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense(DemoCommon.FindLicenseKey())
SkinManager.LoadAssembly(GetType(VioletTheme).Assembly)
+
Application.EnableVisualStyles()
Application.SetCompatibleTextRenderingDefault(False)
Application.Run(New Form1())
@@ -127,10 +132,11 @@ End Module
sfDataGrid1.ThemeName = "VioletTheme"
{% endhighlight %}
+
{% endtabs %}
**Step 3:**
Compile and run the Windows Forms application and you can now witness the custom theme applied to SfDataGrid control at run-time.
-
+
\ No newline at end of file
|