Update getting started winforms .NET 9 (#1934)

* Update winforms getting started

* Minor fix

* unrelated version number fixes

* More updates to wording and style

* Fix number

* fix click vs select

* Update projects to 9

dotnet-desktop-guide/net/winforms/controls-design/designer-differences-framework.md

@@ -1,7 +1,7 @@
 ---
 title: Designers changes from .NET Framework
 description: Learn about the Windows Forms designer changes from .NET Framework to .NET.
-ms.date: 06/01/2023
+ms.date: 11/14/2024
 ms.topic: overview
 no-loc: ["UserControl", "UserControl1", "UserControlProject", "Label", "Button", "Form", "TextBox"]
 dev_langs:
@@ -17,7 +17,7 @@ Visual Studio is a .NET Framework-based application, and as such, the Visual Des
 
 ## Out-of-process designer
 
-The out-of-process designer is a process called **DesignToolsServer.exe**, and is run along-side Visual Studio's **devenv.exe** process. The **DesignToolsServer.exe** process runs on the same version and platform of .NET that your app has been set up to target, such as .NET 7 and x64.
+The out-of-process designer is a process called **DesignToolsServer.exe**, and is run along-side Visual Studio's **devenv.exe** process. The **DesignToolsServer.exe** process runs on the same version and platform of .NET that your app has been set up to target, such as .NET 9 and x64.
 
 In the Visual Studio designer, .NET Framework proxy objects are created for each component and control on the designer, which communicate with the real .NET objects from your project in the **DesignToolsServer.exe** designer.
 

dotnet-desktop-guide/net/winforms/controls-design/designer-overview.md

@@ -30,7 +30,7 @@ Many basic design elements of custom controls have remained the same from .NET F
 
 Visual Studio is a .NET Framework-based application, and as such, the Visual Designer you see for Windows Forms is also based on .NET Framework. With a .NET Framework project, both the Visual Studio environment and the Windows Forms app being designed run within the same process, **devenv.exe**. This poses a problem when you're working with a Windows Forms .NET (not .NET Framework) app. Both .NET and .NET Framework can't work within the same process. As a result, Windows Forms .NET uses a different designer, the "out-of-process" designer.
 
-The out-of-process designer is a process called **DesignToolsServer.exe**, and is run along-side Visual Studio's **devenv.exe** process. The **DesignToolsServer.exe** process runs in the same version and platform, such as .NET 7 and x64, of .NET that your app is targeting. When your custom control needs to display UI in the **devenv.exe** your custom control must implement a client-server architecture to facilitate the communication to and from **devenv.exe**. For more information, see [The designer changes since .NET Framework (Windows Forms .NET)](designer-differences-framework.md).
+The out-of-process designer is a process called **DesignToolsServer.exe**, and is run along-side Visual Studio's **devenv.exe** process. The **DesignToolsServer.exe** process runs in the same version and platform, such as .NET 9 and x64, of .NET that your app is targeting. When your custom control needs to display UI in the **devenv.exe** your custom control must implement a client-server architecture to facilitate the communication to and from **devenv.exe**. For more information, see [The designer changes since .NET Framework (Windows Forms .NET)](designer-differences-framework.md).
 
 ## Property window
 

dotnet-desktop-guide/net/winforms/get-started/snippets/create-app-visual-studio/csharp/Names.csproj

@@ -2,7 +2,7 @@
 
   <PropertyGroup>
     <OutputType>WinExe</OutputType>
-    <TargetFramework>net7.0-windows</TargetFramework>
+    <TargetFramework>net9.0-windows</TargetFramework>
     <Nullable>enable</Nullable>
     <UseWindowsForms>true</UseWindowsForms>
     <ImplicitUsings>enable</ImplicitUsings>

dotnet-desktop-guide/net/winforms/get-started/snippets/create-app-visual-studio/vb/NamesVB.vbproj

@@ -2,7 +2,7 @@
 
   <PropertyGroup>
     <OutputType>WinExe</OutputType>
-    <TargetFramework>net7.0-windows</TargetFramework>
+    <TargetFramework>net9.0-windows</TargetFramework>
     <StartupObject>Sub Main</StartupObject>
     <UseWindowsForms>true</UseWindowsForms>
     <MyType>WindowsForms</MyType>

dotnet-desktop-guide/net/winforms/overview/index.md

@@ -1,7 +1,7 @@
 ---
 title: What is Windows Forms
 description: This article gives an overview of Windows Forms with .NET
-ms.date: 11/15/2021
+ms.date: 11/14/2024
 ms.topic: overview
 #Customer intent: As a developer, I want to understand the components of Windows Forms so that I can understand the overall picture of Windows Forms.
 ---
@@ -14,15 +14,15 @@ There are two implementations of Windows Forms:
 
 01. The open-source implementation hosted on [GitHub](https://github.com/dotnet/winforms).
 
-    This version runs on .NET 6+. The Windows Forms Visual Designer requires, at a minimum, [Visual Studio 2019 version 16.8](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=learn.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019+desktopguide+winforms).
+    This version runs on .NET 6 and later versions.
 
-    The latest version is Windows Forms for .NET 7 using [Visual Studio 2022 version 17.4](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=learn.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2022+desktopguide+winforms).
+    The latest version is Windows Forms for .NET 9 using [Visual Studio 2022 version 17.12](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=learn.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2022+desktopguide+winforms).
 
 01. The .NET Framework 4 implementation that's supported by Visual Studio 2022, Visual Studio 2019, and Visual Studio 2017.
 
     .NET Framework 4 is a Windows-only version of .NET and is considered a Windows Operating System component. This version of Windows Forms is distributed with .NET Framework.
 
-This Desktop Guide is written for Windows Forms on .NET 5 and later versions. For more information about the .NET Framework version of Windows Forms, see [Windows Forms for .NET Framework](../../../framework/winforms/index.yml?view=netframeworkdesktop-4.8&preserve-view=true).
+    For more information about the .NET Framework version of Windows Forms, see [Windows Forms for .NET Framework](../../../framework/winforms/index.yml?view=netframeworkdesktop-4.8&preserve-view=true).
 
 ## Introduction
 
@@ -34,7 +34,7 @@ To learn how to create a Windows Forms app, see [Tutorial: Create a new WinForms
 
 ## Why migrate from .NET Framework
 
-Windows Forms for .NET provides new features and enhancements over .NET Framework. For more information, see [What's new in Windows Forms for .NET 7](../whats-new/net70.md). To learn how to upgrade an app, see [How to upgrade a Windows Forms desktop app to .NET 7](../migration/index.md)
+Windows Forms for .NET provides new features and enhancements over .NET Framework. For more information, see [What's new in Windows Forms for .NET 9](../whats-new/net70.md). To learn how to upgrade an app, see [How to upgrade a Windows Forms desktop app to .NET](../migration/index.md)
 
 ## Build rich, interactive user interfaces
 

dotnet-desktop-guide/net/winforms/wfdev-diagnostics/obsoletions-overview.md

@@ -1,11 +1,11 @@
 ---
-title: Obsolete Windows Forms features in .NET 7+
+title: Obsolete Windows Forms features in .NET
 titleSuffix: ""
 description: Learn about Windows Forms APIs that are marked as obsolete in .NET 7 and later versions that produce WFDEV compiler warnings.
-ms.date: 01/30/2023
+ms.date: 11/14/2024
 ---
 
-# Obsolete Windows Forms features in .NET 7+
+# Obsolete Windows Forms features in .NET
 
 Starting in .NET 7, some Windows Forms APIs are marked as obsolete (or otherwise produce a warning) with custom diagnostic IDs of the format `WFDEVXXX`.
 
@@ -60,5 +60,5 @@ To suppress the warnings in a project file:
 
 ## See also
 
-- [Obsolete .NET features in .NET 5+](/dotnet/fundamentals/syslib-diagnostics/obsoletions-overview)
+- [Obsolete .NET features](/dotnet/fundamentals/syslib-diagnostics/obsoletions-overview)
 <!-- - (add link to breaking change page here...)-->

dotnet-desktop-guide/net/winforms/whats-new/net60.md

@@ -248,4 +248,4 @@ Microsoft UI Automation patterns work better with accessibility tools like Narra
 
 - [Breaking changes in Windows Forms](/dotnet/core/compatibility/winforms)
 - [Tutorial: Create a new WinForms app](../get-started/create-app-visual-studio.md)
-- [How to upgrade a Windows Forms desktop app to .NET 7](../migration/index.md)
+- [How to upgrade a Windows Forms desktop app to .NET](../migration/index.md)