From cf0c95c6a03ed4452d98936ba82009326dc01f26 Mon Sep 17 00:00:00 2001 From: Bhaskar Suresh <102359766+BhaskarSuresh22@users.noreply.github.com> Date: Thu, 20 Nov 2025 10:52:31 +0530 Subject: [PATCH 1/2] WF-993675_Prepared documentation for designer limitations in Tools-Windows controls in NET Core --- WindowsForms/Radial-Menu/Getting-Started.md | 3 +++ WindowsForms/Status-Bar/Getting-Started.md | 2 ++ WindowsForms/Tree-Navigator/Getting-Started.md | 5 ++++- WindowsForms/Wizard-Control/Getting-Started.md | 3 +++ 4 files changed, 12 insertions(+), 1 deletion(-) diff --git a/WindowsForms/Radial-Menu/Getting-Started.md b/WindowsForms/Radial-Menu/Getting-Started.md index 4dc04f508..14d9ba550 100644 --- a/WindowsForms/Radial-Menu/Getting-Started.md +++ b/WindowsForms/Radial-Menu/Getting-Started.md @@ -53,6 +53,9 @@ Menu items can be added into RadialMenu using `Items` collection in Smart Tags o ![Adding Menu Items in windows forms radial menu](Getting-Started_images/RadialMenu-img3.png) +N> Please be aware of a known limitation: if you try to add child items to a RadialMenuItem directly from the Visual Studio Properties window, it will open the default Collection Editor. +Workaround: You can add child items by opening the main RadialMenu's Collection Editor and then accessing the collection for the specific RadialMenuItem from within that editor. We have identified this behaviour and are actively working on a permanent fix. + ## Adding control manually using code To add control manually in C#, follow the given steps: diff --git a/WindowsForms/Status-Bar/Getting-Started.md b/WindowsForms/Status-Bar/Getting-Started.md index 90dc87461..80d6a030f 100644 --- a/WindowsForms/Status-Bar/Getting-Started.md +++ b/WindowsForms/Status-Bar/Getting-Started.md @@ -25,6 +25,8 @@ To create a StatusBarAdv control through designer, ![Run the application in WindowsForms-Status Bar](overview_images/windowsforms-status-bar-run-application.jpeg) +N> In .NET Core, the StatusBarAdv control’s Collection Editor displays the title “ControlProxy`1 CollectionEditor” instead of “StatusBarAdvPanel CollectionEditor.” This is a known issue that does not affect functionality; it has been logged, and we will provide updates as they become available. +GitHub - [Issue #14049](https://github.com/dotnet/winforms/issues/14049) ## Through code diff --git a/WindowsForms/Tree-Navigator/Getting-Started.md b/WindowsForms/Tree-Navigator/Getting-Started.md index 3ef2fa243..56c8be107 100644 --- a/WindowsForms/Tree-Navigator/Getting-Started.md +++ b/WindowsForms/Tree-Navigator/Getting-Started.md @@ -165,4 +165,7 @@ The following steps allows you to add TreeMenuItem to the TreeNavigator through ![Adding the Items](Getting-Started_images/ThroughDesigner2.png) -![TreeNavigator Output](Getting-Started_images/Adding_TreeMenuitems.png) \ No newline at end of file +![TreeNavigator Output](Getting-Started_images/Adding_TreeMenuitems.png) + +N> Please be aware of a known limitation: if you try to add child items to a TreeMenuItem directly from the Visual Studio Properties window, it will open the default Collection Editor. +Workaround: You can add child items by opening the main TreeNavigator Collection Editor and then accessing the collection for the specific TreeMenuItem from within that editor. We have identified this behaviour and are actively working on a permanent fix. \ No newline at end of file diff --git a/WindowsForms/Wizard-Control/Getting-Started.md b/WindowsForms/Wizard-Control/Getting-Started.md index 7b8bb113b..5cc7924b1 100644 --- a/WindowsForms/Wizard-Control/Getting-Started.md +++ b/WindowsForms/Wizard-Control/Getting-Started.md @@ -48,6 +48,9 @@ The [WizardControl](https://help.syncfusion.com/cr/windowsforms/Syncfusion.Windo ![Drag and drop the wizard control to form](Getting-Started_images/GettingStarted-img2.png) +N> In .NET Core, the Wizard control’s Collection Editor displays the title “ControlProxy`1 CollectionEditor” instead of “WizardControlPage CollectionEditor.” This is a known issue that does not affect functionality; it has been logged, and we will provide updates as they become available. +GitHub - [Issue #14049](https://github.com/dotnet/winforms/issues/14049) + ## Adding control manually in code To add control manually in C#, follow the given steps: From 965b975d1c608171738c83bc84afcb15e329dc7b Mon Sep 17 00:00:00 2001 From: Bhaskar Suresh <102359766+BhaskarSuresh22@users.noreply.github.com> Date: Tue, 25 Nov 2025 13:23:41 +0530 Subject: [PATCH 2/2] Modified the release notes content --- WindowsForms/Radial-Menu/Getting-Started.md | 4 ++-- WindowsForms/Status-Bar/Getting-Started.md | 5 +++-- WindowsForms/Tree-Navigator/Getting-Started.md | 4 ++-- WindowsForms/Wizard-Control/Getting-Started.md | 5 +++-- 4 files changed, 10 insertions(+), 8 deletions(-) diff --git a/WindowsForms/Radial-Menu/Getting-Started.md b/WindowsForms/Radial-Menu/Getting-Started.md index 14d9ba550..f1b7e520d 100644 --- a/WindowsForms/Radial-Menu/Getting-Started.md +++ b/WindowsForms/Radial-Menu/Getting-Started.md @@ -53,8 +53,8 @@ Menu items can be added into RadialMenu using `Items` collection in Smart Tags o ![Adding Menu Items in windows forms radial menu](Getting-Started_images/RadialMenu-img3.png) -N> Please be aware of a known limitation: if you try to add child items to a RadialMenuItem directly from the Visual Studio Properties window, it will open the default Collection Editor. -Workaround: You can add child items by opening the main RadialMenu's Collection Editor and then accessing the collection for the specific RadialMenuItem from within that editor. We have identified this behaviour and are actively working on a permanent fix. +N> In .NET Core, when adding child items to a RadialMenuItem directly from the Visual Studio Properties window, the default Collection Editor opens instead of the expected editor. +Workaround: Use the main RadialMenu Collection Editor to add items, then configure the child items as needed. A permanent fix is in progress. ## Adding control manually using code diff --git a/WindowsForms/Status-Bar/Getting-Started.md b/WindowsForms/Status-Bar/Getting-Started.md index 80d6a030f..5de9b23c9 100644 --- a/WindowsForms/Status-Bar/Getting-Started.md +++ b/WindowsForms/Status-Bar/Getting-Started.md @@ -25,8 +25,9 @@ To create a StatusBarAdv control through designer, ![Run the application in WindowsForms-Status Bar](overview_images/windowsforms-status-bar-run-application.jpeg) -N> In .NET Core, the StatusBarAdv control’s Collection Editor displays the title “ControlProxy`1 CollectionEditor” instead of “StatusBarAdvPanel CollectionEditor.” This is a known issue that does not affect functionality; it has been logged, and we will provide updates as they become available. -GitHub - [Issue #14049](https://github.com/dotnet/winforms/issues/14049) +N> In .NET Core, the StatusBarAdv control’s Collection Editor displays the title “ControlProxy`1 CollectionEditor” instead of “StatusBarAdvPanel CollectionEditor.” +This is a known issue and does not affect functionality. +For more details, see GitHub Issue [#14049](https://github.com/dotnet/winforms/issues/14049) ## Through code diff --git a/WindowsForms/Tree-Navigator/Getting-Started.md b/WindowsForms/Tree-Navigator/Getting-Started.md index 56c8be107..e1dea38f7 100644 --- a/WindowsForms/Tree-Navigator/Getting-Started.md +++ b/WindowsForms/Tree-Navigator/Getting-Started.md @@ -167,5 +167,5 @@ The following steps allows you to add TreeMenuItem to the TreeNavigator through ![TreeNavigator Output](Getting-Started_images/Adding_TreeMenuitems.png) -N> Please be aware of a known limitation: if you try to add child items to a TreeMenuItem directly from the Visual Studio Properties window, it will open the default Collection Editor. -Workaround: You can add child items by opening the main TreeNavigator Collection Editor and then accessing the collection for the specific TreeMenuItem from within that editor. We have identified this behaviour and are actively working on a permanent fix. \ No newline at end of file +N> In .NET Core, when adding child items to a TreeMenuItem directly from the Visual Studio Properties window, the default Collection Editor opens instead of the expected editor. +Workaround: Use the main TreeNavigator Collection Editor to add items, then configure the child items as needed. A permanent fix is in progress. \ No newline at end of file diff --git a/WindowsForms/Wizard-Control/Getting-Started.md b/WindowsForms/Wizard-Control/Getting-Started.md index 5cc7924b1..f3f245d02 100644 --- a/WindowsForms/Wizard-Control/Getting-Started.md +++ b/WindowsForms/Wizard-Control/Getting-Started.md @@ -48,8 +48,9 @@ The [WizardControl](https://help.syncfusion.com/cr/windowsforms/Syncfusion.Windo ![Drag and drop the wizard control to form](Getting-Started_images/GettingStarted-img2.png) -N> In .NET Core, the Wizard control’s Collection Editor displays the title “ControlProxy`1 CollectionEditor” instead of “WizardControlPage CollectionEditor.” This is a known issue that does not affect functionality; it has been logged, and we will provide updates as they become available. -GitHub - [Issue #14049](https://github.com/dotnet/winforms/issues/14049) +N> In .NET Core, the Wizard control’s Collection Editor displays the title “ControlProxy`1 CollectionEditor” instead of “WizardControlPage CollectionEditor.” +This is a known issue and does not affect functionality. +For more details, see GitHub Issue [#14049](https://github.com/dotnet/winforms/issues/14049) ## Adding control manually in code