From bdd3064482cfd871bf708f571b33bf4c5960da04 Mon Sep 17 00:00:00 2001 From: "Andy De George (adegeo)" Date: Thu, 31 Aug 2023 15:25:28 -0700 Subject: [PATCH 1/2] Update message and add new intro msg --- ...debugging-custom-windows-forms-controls-at-design-time.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/dotnet-desktop-guide/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time.md b/dotnet-desktop-guide/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time.md index 37460fd1f1..c7d145e4ea 100644 --- a/dotnet-desktop-guide/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time.md +++ b/dotnet-desktop-guide/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time.md @@ -23,6 +23,9 @@ When you create a custom control, you will often find it necessary to debug its You can debug your custom controls using Visual Studio, just as you would debug any other .NET Framework classes. The difference is that you will debug a separate instance of Visual Studio that is running your custom control's code. +> [!IMPORTANT] +> This article is primarily intended for the classic In-Process Designer for Windows Forms with .NET Framework. The procedures may not be directly applicable or fully compatible with projects that target .NET. Further, Visual Studio 2022 runs on .NET Framework 4.7.2 in a 64-bit environment, which can cause compatibility issues with Out-Of-Process Designers if you target a 32-bit architecture with your .NET applications. For more information about the Out-Of-Process Designer, see [The designer changes since .NET Framework](../../../net/winforms/controls-design/designer-differences-framework.md). + ## Create the project The first step is to create the application project. You will use this project to build the application that hosts the custom control. @@ -126,7 +129,7 @@ Now you are ready to debug your custom control as it runs in design mode. When y 3. In the new instance of Visual Studio, open the "DebuggingExample" solution. You can easily find the solution by selecting **Recent Projects** from the **File** menu. The "DebuggingExample.sln" solution file will be listed as the most recently used file. > [!IMPORTANT] - > If you're debugging a .NET 5 (.NET Core 3.1) or later Windows Forms project, use this instance of Visual Studio to attach a debugger to the the *DesignToolsServer.exe* process. Select the **Debug** > **Attach to process** menu item. Find *DesignToolsServer.exe* in the list of processes and press **Attach**. + > If you're debugging a .NET 6 or later Windows Forms project, don't load the project, instead, use this instance of Visual Studio to attach a debugger to the the *DesignToolsServer.exe* process. Select the **Debug** > **Attach to process** menu item. Find *DesignToolsServer.exe* in the list of processes and press **Attach**. For more information, see [The designer changes since .NET Framework](../../../net/winforms/controls-design/designer-differences-framework.md). 4. Open Form1 in the **Forms Designer** and select the **DebugControl** control. From 0bb97ea91c95e6d44af3bf6aa0a93cbec4856e6f Mon Sep 17 00:00:00 2001 From: "Andy (Steve) De George" <67293991+adegeo@users.noreply.github.com> Date: Wed, 20 Sep 2023 16:00:34 -0700 Subject: [PATCH 2/2] Update dotnet-desktop-guide/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Klaus Löffelmann <9663150+KlausLoeffelmann@users.noreply.github.com> --- ...ebugging-custom-windows-forms-controls-at-design-time.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/dotnet-desktop-guide/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time.md b/dotnet-desktop-guide/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time.md index c7d145e4ea..4a92bfb8fc 100644 --- a/dotnet-desktop-guide/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time.md +++ b/dotnet-desktop-guide/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time.md @@ -24,7 +24,11 @@ When you create a custom control, you will often find it necessary to debug its You can debug your custom controls using Visual Studio, just as you would debug any other .NET Framework classes. The difference is that you will debug a separate instance of Visual Studio that is running your custom control's code. > [!IMPORTANT] -> This article is primarily intended for the classic In-Process Designer for Windows Forms with .NET Framework. The procedures may not be directly applicable or fully compatible with projects that target .NET. Further, Visual Studio 2022 runs on .NET Framework 4.7.2 in a 64-bit environment, which can cause compatibility issues with Out-Of-Process Designers if you target a 32-bit architecture with your .NET applications. For more information about the Out-Of-Process Designer, see [The designer changes since .NET Framework](../../../net/winforms/controls-design/designer-differences-framework.md). +> This article is primarily intended for the classic In-Process Designer for Windows Forms with .NET Framework. The procedures may not be directly applicable or fully compatible with projects that target .NET (not .NET Framework). +> +> For .NET Framework projects, only projects that can compile with the platform target settings _Any_ or _x64_ are fully supported in the Designer. Projects that use ActiveX, COM, or other 32-bit components, may have compatibility issues. The Out-Of_Process Framework Designer, currently in preview, addresses many of those compatibility issues. However, design-time functionality may not work as well as the 64-bit In-Process Designer. To enable the Out-Of-Process Framework Designer, navigate to the **Tools** > **Options** > **Environment** > **Preview Features**. +> +> For more information about the Out-Of-Process Designer, see [The designer changes since .NET Framework](../../../net/winforms/controls-design/designer-differences-framework.md). ## Create the project