Update WinForms link URLs

xml/Microsoft.VisualBasic.Compatibility.VB6/Support.xml

@@ -2003,13 +2003,13 @@
 ## Remarks
  In Visual Basic 6.0, international versions of an application were created by putting all localizable information, such as strings, into a separate resource file (.res) for each language. At run time, locale-specific resources were loaded from the resource file by calling the `LoadResString`, `LoadResPicture`, and `LoadResData` functions.
 
- In Visual Basic, international versions of an application are created by changing the `Language` property of a form at design time. A separate resource file (.resx) is automatically created for each locale selected. You no longer have to explicitly load resources from code; resources are automatically loaded based on the user's locale. For more information, see [Globalizing Windows Forms applications](/dotnet/framework/winforms/advanced/globalizing-windows-forms).  
+ In Visual Basic, international versions of an application are created by changing the `Language` property of a form at design time. A separate resource file (.resx) is automatically created for each locale selected. You no longer have to explicitly load resources from code; resources are automatically loaded based on the user's locale. For more information, see [Globalizing Windows Forms applications](/dotnet/desktop/winforms/advanced/globalizing-windows-forms).
 
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]
 
  ]]></format>
         </remarks>
-        <related type="Article" href="/dotnet/framework/winforms/advanced/globalizing-windows-forms">Globalizing Windows Forms</related>
+        <related type="Article" href="/dotnet/desktop/winforms/advanced/globalizing-windows-forms">Globalizing Windows Forms</related>
       </Docs>
     </Member>
     <Member MemberName="LoadResData">
@@ -2051,13 +2051,13 @@
 ## Remarks
  In Visual Basic 6.0, international versions of an application were created by putting all localizable information, such as strings, into a separate resource file (.res) for each language. At run time, locale-specific resources were loaded from the resource file by calling the `LoadResString`, `LoadResPicture`, and `LoadResData` functions.
 
- In Visual Basic, international versions of an application are created by changing the `Language` property of a form at design time. A separate resource file (.resx) is automatically created for each locale selected. You no longer have to explicitly load resources from code; resources are automatically loaded based on the user's locale. For more information, see [Globalizing Windows Forms applications](/dotnet/framework/winforms/advanced/globalizing-windows-forms).  
+ In Visual Basic, international versions of an application are created by changing the `Language` property of a form at design time. A separate resource file (.resx) is automatically created for each locale selected. You no longer have to explicitly load resources from code; resources are automatically loaded based on the user's locale. For more information, see [Globalizing Windows Forms applications](/dotnet/desktop/winforms/advanced/globalizing-windows-forms).
 
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]
 
  ]]></format>
         </remarks>
-        <related type="Article" href="/dotnet/framework/winforms/advanced/globalizing-windows-forms">Globalizing Windows Forms</related>
+        <related type="Article" href="/dotnet/desktop/winforms/advanced/globalizing-windows-forms">Globalizing Windows Forms</related>
       </Docs>
     </Member>
     <MemberGroup MemberName="LoadResPicture">
@@ -2106,13 +2106,13 @@
 ## Remarks
  In Visual Basic 6.0, international versions of an application were created by putting all localizable information, such as strings, into a separate resource file (.res) for each language. At run time, locale-specific resources were loaded from the resource file by calling the `LoadResString`, `LoadResPicture`, and `LoadResData` functions.
 
- In Visual Basic, international versions of an application are created by changing the `Language` property of a form at design time. A separate resource file (.resx) is automatically created for each locale selected. You no longer have to explicitly load resources from code; resources are automatically loaded based on the user's locale. For more information, see [Globalizing Windows Forms applications](/dotnet/framework/winforms/advanced/globalizing-windows-forms).  
+ In Visual Basic, international versions of an application are created by changing the `Language` property of a form at design time. A separate resource file (.resx) is automatically created for each locale selected. You no longer have to explicitly load resources from code; resources are automatically loaded based on the user's locale. For more information, see [Globalizing Windows Forms applications](/dotnet/desktop/winforms/advanced/globalizing-windows-forms).
 
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]
 
  ]]></format>
         </remarks>
-        <related type="Article" href="/dotnet/framework/winforms/advanced/globalizing-windows-forms">Globalizing Windows Forms</related>
+        <related type="Article" href="/dotnet/desktop/winforms/advanced/globalizing-windows-forms">Globalizing Windows Forms</related>
       </Docs>
     </Member>
     <Member MemberName="LoadResPicture">
@@ -2154,13 +2154,13 @@
 ## Remarks
  In Visual Basic 6.0, international versions of an application were created by putting all localizable information, such as strings, into a separate resource file (.res) for each language. At run time, locale-specific resources were loaded from the resource file by calling the `LoadResString`, `LoadResPicture`, and `LoadResData` functions.
 
- In Visual Basic, international versions of an application are created by changing the `Language` property of a form at design time. A separate resource file (.resx) is automatically created for each locale selected. You no longer have to explicitly load resources from code; resources are automatically loaded based on the user's locale. For more information, see [Globalizing Windows Forms applications](/dotnet/framework/winforms/advanced/globalizing-windows-forms).  
+ In Visual Basic, international versions of an application are created by changing the `Language` property of a form at design time. A separate resource file (.resx) is automatically created for each locale selected. You no longer have to explicitly load resources from code; resources are automatically loaded based on the user's locale. For more information, see [Globalizing Windows Forms applications](/dotnet/desktop/winforms/advanced/globalizing-windows-forms).
 
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]
 
  ]]></format>
         </remarks>
-        <related type="Article" href="/dotnet/framework/winforms/advanced/globalizing-windows-forms">Globalizing Windows Forms</related>
+        <related type="Article" href="/dotnet/desktop/winforms/advanced/globalizing-windows-forms">Globalizing Windows Forms</related>
       </Docs>
     </Member>
     <MemberGroup MemberName="LoadResString">
@@ -2207,13 +2207,13 @@
 ## Remarks
  In Visual Basic 6.0, international versions of an application were created by putting all localizable information, such as strings, into a separate resource file (.res) for each language. At run time, locale-specific resources were loaded from the resource file by calling the `LoadResString`, `LoadResPicture`, and `LoadResData` functions.
 
- In Visual Basic, international versions of an application are created by changing the `Language` property of a form at design time. A separate resource file (.resx) is automatically created for each locale selected. You no longer have to explicitly load resources from code; resources are automatically loaded based on the user's locale. For more information, see [Globalizing Windows Forms applications](/dotnet/framework/winforms/advanced/globalizing-windows-forms).  
+ In Visual Basic, international versions of an application are created by changing the `Language` property of a form at design time. A separate resource file (.resx) is automatically created for each locale selected. You no longer have to explicitly load resources from code; resources are automatically loaded based on the user's locale. For more information, see [Globalizing Windows Forms applications](/dotnet/desktop/winforms/advanced/globalizing-windows-forms).
 
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]
 
  ]]></format>
         </remarks>
-        <related type="Article" href="/dotnet/framework/winforms/advanced/globalizing-windows-forms">Globalizing Windows Forms</related>
+        <related type="Article" href="/dotnet/desktop/winforms/advanced/globalizing-windows-forms">Globalizing Windows Forms</related>
       </Docs>
     </Member>
     <Member MemberName="LoadResString">
@@ -2253,13 +2253,13 @@
 ## Remarks
  In Visual Basic 6.0, international versions of an application were created by putting all localizable information, such as strings, into a separate resource file (.res) for each language. At run time, locale-specific resources were loaded from the resource file by calling the `LoadResString`, `LoadResPicture`, and `LoadResData` functions.
 
- In Visual Basic, international versions of an application are created by changing the `Language` property of a form at design time. A separate resource file (.resx) is automatically created for each locale selected. You no longer have to explicitly load resources from code; resources are automatically loaded based on the user's locale. For more information, see [Globalizing Windows Forms applications](/dotnet/framework/winforms/advanced/globalizing-windows-forms).  
+ In Visual Basic, international versions of an application are created by changing the `Language` property of a form at design time. A separate resource file (.resx) is automatically created for each locale selected. You no longer have to explicitly load resources from code; resources are automatically loaded based on the user's locale. For more information, see [Globalizing Windows Forms applications](/dotnet/desktop/winforms/advanced/globalizing-windows-forms).
 
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]
 
  ]]></format>
         </remarks>
-        <related type="Article" href="/dotnet/framework/winforms/advanced/globalizing-windows-forms">Globalizing Windows Forms</related>
+        <related type="Article" href="/dotnet/desktop/winforms/advanced/globalizing-windows-forms">Globalizing Windows Forms</related>
       </Docs>
     </Member>
     <Member MemberName="PixelsToTwipsX">

xml/Microsoft.VisualBasic.Devices/Ports.xml

@@ -599,7 +599,7 @@
 ## Examples
  This example loops over all the strings that the `My.Computer.Ports.SerialPortNames` property returns. These strings are the names of the available serial ports on the computer.
 
- Typically, a user selects which serial port the application should use from the list of available ports. In this example, the serial port names are stored in a <xref:System.Windows.Forms.ListBox> control. For more information, see [ListBox Control](/dotnet/framework/winforms/controls/listbox-control-windows-forms).  
+ Typically, a user selects which serial port the application should use from the list of available ports. In this example, the serial port names are stored in a <xref:System.Windows.Forms.ListBox> control. For more information, see [ListBox Control](/dotnet/desktop/winforms/controls/listbox-control-windows-forms).
 
  :::code language="vb" source="~/snippets/visualbasic/VS_Snippets_VBCSharp/VbVbalrMyComputer/VB/Class2.vb" id="Snippet45":::
 

xml/Microsoft.VisualBasic.MyServices/ClipboardProxy.xml

@@ -111,7 +111,7 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The <xref:System.Security.Permissions.UIPermission> class controls access to the Clipboard, and the associated <xref:System.Security.Permissions.UIPermissionClipboard> enumeration value indicates the level of access. For more information, see [Additional Security Considerations in Windows Forms](/dotnet/framework/winforms/additional-security-considerations-in-windows-forms).  
+ The <xref:System.Security.Permissions.UIPermission> class controls access to the Clipboard, and the associated <xref:System.Security.Permissions.UIPermissionClipboard> enumeration value indicates the level of access. For more information, see [Additional Security Considerations in Windows Forms](/dotnet/desktop/winforms/additional-security-considerations-in-windows-forms).
 
 ## Availability by Project Type
 

xml/System.Configuration/ApplicationScopedSettingAttribute.xml

@@ -53,7 +53,7 @@
     <altmember cref="T:System.Configuration.ApplicationSettingsBase" />
     <altmember cref="T:System.Configuration.SettingsProvider" />
     <altmember cref="T:System.Configuration.ConfigurationErrorsException" />
-    <related type="Article" href="/dotnet/framework/winforms/advanced/application-settings-architecture">Application Settings Architecture</related>
+    <related type="Article" href="/dotnet/desktop/winforms/advanced/application-settings-architecture">Application Settings Architecture</related>
   </Docs>
   <Members>
     <Member MemberName=".ctor">

xml/System.Configuration/ApplicationSettingsBase.xml

@@ -63,7 +63,7 @@
 
  By default, all client-based applications use the <xref:System.Configuration.LocalFileSettingsProvider> to provide storage. If an alternate settings provider is desired, then the wrapper class or property must be decorated with a corresponding <xref:System.Configuration.SettingsProviderAttribute>.
 
- For more information about using application settings, see [Application Settings for Windows Forms](/dotnet/framework/winforms/advanced/application-settings-for-windows-forms).  
+ For more information about using application settings, see [Application Settings for Windows Forms](/dotnet/desktop/winforms/advanced/application-settings-for-windows-forms).
 
 
 
@@ -95,7 +95,7 @@
     <altmember cref="T:System.Configuration.UserScopedSettingAttribute" />
     <altmember cref="T:System.Configuration.SettingsGroupNameAttribute" />
     <altmember cref="T:System.Configuration.SettingsProviderAttribute" />
-    <related type="Article" href="/dotnet/framework/winforms/advanced/application-settings-for-windows-forms">Application Settings for Windows Forms</related>
+    <related type="Article" href="/dotnet/desktop/winforms/advanced/application-settings-for-windows-forms">Application Settings for Windows Forms</related>
   </Docs>
   <Members>
     <MemberGroup MemberName=".ctor">
@@ -1083,7 +1083,7 @@
 ## Remarks
  The <xref:System.Configuration.ApplicationSettingsBase.SettingChanging> event occurs before an application setting value property is changed through the <xref:System.Configuration.ApplicationSettingsBase.Item%2A> method. This event is not raised when the <xref:System.Configuration.ApplicationSettingsBase.Reload%2A> or <xref:System.Configuration.ApplicationSettingsBase.Reset%2A> methods are called. <xref:System.Configuration.ApplicationSettingsBase.SettingChanging> can be canceled through the <xref:System.Configuration.SettingChangingEventArgs> event data class.
 
- You typically use the <xref:System.Configuration.ApplicationSettingsBase.SettingChanging> event to handle immediate validation of an individual settings property. For more information about validation, see [How to: Validate Application Settings](/dotnet/framework/winforms/advanced/how-to-validate-application-settings).  
+ You typically use the <xref:System.Configuration.ApplicationSettingsBase.SettingChanging> event to handle immediate validation of an individual settings property. For more information about validation, see [How to: Validate Application Settings](/dotnet/desktop/winforms/advanced/how-to-validate-application-settings).
 
  There is no corresponding `SettingChanged` event for this class; instead, see the <xref:System.Configuration.ApplicationSettingsBase.PropertyChanged> event.
 
@@ -1102,7 +1102,7 @@
         <altmember cref="T:System.Configuration.SettingChangingEventArgs" />
         <altmember cref="E:System.Configuration.ApplicationSettingsBase.PropertyChanged" />
         <altmember cref="P:System.Configuration.ApplicationSettingsBase.Item(System.String)" />
-        <related type="Article" href="/dotnet/framework/winforms/advanced/how-to-validate-application-settings">How to: Validate Application Settings</related>
+        <related type="Article" href="/dotnet/desktop/winforms/advanced/how-to-validate-application-settings">How to: Validate Application Settings</related>
       </Docs>
     </Member>
     <Member MemberName="SettingsKey">

xml/System.Configuration/ClientSettingsSection.xml

@@ -40,14 +40,14 @@
 
  The <xref:System.Configuration.ClientSettingsSection> class represents a simple extension of the <xref:System.Configuration.ConfigurationSection> class, which is used in the .NET Framework support for general configuration files.
 
- For more information about application settings, see the topic [Application Settings for Windows Forms](/dotnet/framework/winforms/advanced/application-settings-for-windows-forms).  
+ For more information about application settings, see the topic [Application Settings for Windows Forms](/dotnet/desktop/winforms/advanced/application-settings-for-windows-forms).
 
  ]]></format>
     </remarks>
     <altmember cref="T:System.Configuration.LocalFileSettingsProvider" />
     <altmember cref="T:System.Configuration.AppSettingsSection" />
     <altmember cref="T:System.Configuration.IConfigurationSectionHandler" />
-    <related type="Article" href="/dotnet/framework/winforms/advanced/application-settings-for-windows-forms">Application Settings for Windows Forms</related>
+    <related type="Article" href="/dotnet/desktop/winforms/advanced/application-settings-for-windows-forms">Application Settings for Windows Forms</related>
   </Docs>
   <Members>
     <Member MemberName=".ctor">

xml/System.Configuration/DefaultSettingValueAttribute.xml

@@ -68,7 +68,7 @@
     <altmember cref="T:System.Configuration.SettingsProvider" />
     <altmember cref="T:System.Configuration.LocalFileSettingsProvider" />
     <altmember cref="T:System.Configuration.SettingsSerializeAsAttribute" />
-    <related type="Article" href="/dotnet/framework/winforms/advanced/application-settings-for-windows-forms">Application Settings for Windows Forms</related>
+    <related type="Article" href="/dotnet/desktop/winforms/advanced/application-settings-for-windows-forms">Application Settings for Windows Forms</related>
   </Docs>
   <Members>
     <Member MemberName=".ctor">

xml/System.Configuration/IApplicationSettingsProvider.xml

@@ -50,7 +50,7 @@
     </remarks>
     <altmember cref="T:System.Configuration.SettingsProvider" />
     <altmember cref="T:System.Configuration.ApplicationSettingsBase" />
-    <related type="Article" href="/dotnet/framework/winforms/advanced/application-settings-architecture">Application Settings Architecture</related>
+    <related type="Article" href="/dotnet/desktop/winforms/advanced/application-settings-architecture">Application Settings Architecture</related>
   </Docs>
   <Members>
     <Member MemberName="GetPreviousVersion">

xml/System.Configuration/IPersistComponentSettings.xml

@@ -38,7 +38,7 @@
  ]]></format>
     </remarks>
     <altmember cref="T:System.Configuration.ApplicationSettingsBase" />
-    <related type="Article" href="/dotnet/framework/winforms/advanced/application-settings-for-custom-controls">Application Settings for Custom Controls</related>
+    <related type="Article" href="/dotnet/desktop/winforms/advanced/application-settings-for-custom-controls">Application Settings for Custom Controls</related>
   </Docs>
   <Members>
     <Member MemberName="LoadComponentSettings">
@@ -302,7 +302,7 @@
         </remarks>
         <altmember cref="M:System.Configuration.IPersistComponentSettings.SaveComponentSettings" />
         <altmember cref="P:System.Configuration.ApplicationSettingsBase.SettingsKey" />
-        <related type="Article" href="/dotnet/framework/winforms/advanced/application-settings-for-custom-controls">Application Settings for Custom Controls</related>
+        <related type="Article" href="/dotnet/desktop/winforms/advanced/application-settings-for-custom-controls">Application Settings for Custom Controls</related>
       </Docs>
     </Member>
   </Members>