From be6d8cca279881d1673a4d3da0bf8c9483606ea4 Mon Sep 17 00:00:00 2001 From: Sachin Fernando <47466168+MFredX@users.noreply.github.com> Date: Mon, 17 Nov 2025 17:26:39 +1100 Subject: [PATCH 1/2] Update disable-dpi-awareness.md --- docs/designers/disable-dpi-awareness.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/designers/disable-dpi-awareness.md b/docs/designers/disable-dpi-awareness.md index 3e3655e7c6c..228edf952f9 100644 --- a/docs/designers/disable-dpi-awareness.md +++ b/docs/designers/disable-dpi-awareness.md @@ -25,6 +25,8 @@ When an application declares itself to be DPI-aware, it's a statement specifying > [!NOTE] > In Visual Studio 2022 version 17.8 or later, you can avoid the issues described in this article. Visual Studio 2022 version 17.8 provides support for DPI-unaware tabs within a DPI-aware application. See [Visual Studio DPI improvements](/dotnet/desktop/winforms/whats-new/net80#visual-studio-dpi-improvements). This lets you design Windows Forms for DPI-unaware contexts, without requiring you to run Visual Studio in DPI-unaware mode. To use this setting in a Windows Forms project, set the property `ForceDesignerDPIUnaware` to `true` in your project file: > +>The `ForceDesignerDpiUnaware` project property is supported only for Windows Forms projects targeting **.NET 6 or later**. Projects targeting **.NET Framework (including .NET Framework 4.8)** do not use this setting; the designer will continue to run with the default DPI behavior. +> >```xml > > ... From 89008ebeec5f23d1f3de47f790af449357ad795d Mon Sep 17 00:00:00 2001 From: Gordon Hogenson Date: Tue, 6 Jan 2026 09:42:59 -0800 Subject: [PATCH 2/2] Update docs/designers/disable-dpi-awareness.md --- docs/designers/disable-dpi-awareness.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/designers/disable-dpi-awareness.md b/docs/designers/disable-dpi-awareness.md index 228edf952f9..fcf70164fec 100644 --- a/docs/designers/disable-dpi-awareness.md +++ b/docs/designers/disable-dpi-awareness.md @@ -23,7 +23,7 @@ When an application declares itself to be DPI-aware, it's a statement specifying :::moniker range=">=vs-2022" > [!NOTE] -> In Visual Studio 2022 version 17.8 or later, you can avoid the issues described in this article. Visual Studio 2022 version 17.8 provides support for DPI-unaware tabs within a DPI-aware application. See [Visual Studio DPI improvements](/dotnet/desktop/winforms/whats-new/net80#visual-studio-dpi-improvements). This lets you design Windows Forms for DPI-unaware contexts, without requiring you to run Visual Studio in DPI-unaware mode. To use this setting in a Windows Forms project, set the property `ForceDesignerDPIUnaware` to `true` in your project file: +> In Visual Studio 2022 version 17.8 or later, you can avoid the issues described in this article. Visual Studio 2022 version 17.8 provides support for DPI-unaware tabs within a DPI-aware application. See [Visual Studio DPI improvements](/dotnet/desktop/winforms/whats-new/net80#visual-studio-dpi-improvements). This lets you design Windows Forms for DPI-unaware contexts, without requiring you to run Visual Studio in DPI-unaware mode. To use this setting in a Windows Forms project, set the property `ForceDesignerDPIUnaware` to `true` in your project file. > >The `ForceDesignerDpiUnaware` project property is supported only for Windows Forms projects targeting **.NET 6 or later**. Projects targeting **.NET Framework (including .NET Framework 4.8)** do not use this setting; the designer will continue to run with the default DPI behavior. >