Merged main into live

mijacobs · mijacobs · commit 6e6080fb909a · 2025-06-17T01:05:02.000Z
diff --git a/docs/get-started/visual-studio-ide.md b/docs/get-started/visual-studio-ide.md
@@ -170,7 +170,7 @@ Select the following button to install Visual Studio, and choose the edition of
 Dive into coding with one of the following language-specific tutorials:
 
 - [Create a simple C# console app](./csharp/tutorial-console.md)
-- [Get started with Python](../python/tutorial-working-with-python-in-visual-studio-step-00-installation.md)
+- [Get started with Python](/visualstudio/python/installing-python-support-in-visual-studio)
 - [Create a simple VB console app](./visual-basic/tutorial-console.md)
 - [Create a C++ console app](/cpp/get-started/tutorial-console-cpp)
 - [Create a Node.js and Express app](../javascript/tutorial-nodejs.md)
diff --git a/docs/install/automated-installation-with-response-file.md b/docs/install/automated-installation-with-response-file.md
@@ -221,7 +221,7 @@ In the following example, the `response.json` file initializes a Visual Studio E
 
 ## Troubleshooting
 
-If you run into a problem with the Visual Studio bootstrapper throwing an error when you pair it with a `response.json` file, see [Troubleshoot network-related errors when you install or use Visual Studio](../install/troubleshooting-network-related-errors-in-visual-studio.md#error-failed-to-parse-id-from-parent-process) page for more information.
+If you run into a problem with the Visual Studio bootstrapper throwing an error when you pair it with a `response.json` file, see [Troubleshoot network-related errors when you install or use Visual Studio](/troubleshoot/developer/visualstudio/installation/troubleshoot-network-related-errors#error-failed-to-parse-id-from-parent-process) page for more information.
 
 [!INCLUDE[install_get_support_md](includes/install_get_support_md.md)]
 
@@ -231,4 +231,4 @@ If you run into a problem with the Visual Studio bootstrapper throwing an error
 * [Deploy Visual Studio from a layout onto a client machine](deploy-a-layout-onto-a-client-machine.md)
 * [Configure policies for enterprise deployments](configure-policies-for-enterprise-deployments.md)
 * [Visual Studio workload and component IDs](workload-and-component-ids.md)
-* [Troubleshoot network-related errors when you install or use Visual Studio](troubleshooting-network-related-errors-in-visual-studio.md)
+* [Troubleshoot network-related errors when you install or use Visual Studio](/troubleshoot/developer/visualstudio/installation/troubleshoot-network-related-errors)
diff --git a/docs/install/create-a-network-installation-of-visual-studio.md b/docs/install/create-a-network-installation-of-visual-studio.md
@@ -414,7 +414,7 @@ We have other support options available, too. See our [Visual Studio Developer C
 - [Visual Studio administrator guide](visual-studio-administrator-guide.md)
 - [Deploy Visual Studio from a layout onto a client machine](deploy-a-layout-onto-a-client-machine.md)
 - [Update a network-based installation of Visual Studio](update-a-network-installation-of-visual-studio.md)
-- [Troubleshoot network-related errors when you install or use Visual Studio](troubleshooting-network-related-errors-in-visual-studio.md)
+- [Troubleshoot network-related errors when you install or use Visual Studio](/troubleshoot/developer/visualstudio/installation/troubleshoot-network-related-errors)
 - [Configure policies for enterprise deployments of Visual Studio](configure-policies-for-enterprise-deployments.md) 
 - [Visual Studio product lifecycle and servicing](/visualstudio/productinfo/vs-servicing/)
 - [Use command-line parameters to install Visual Studio](use-command-line-parameters-to-install-visual-studio.md)
diff --git a/docs/install/deploy-a-layout-onto-a-client-machine.md b/docs/install/deploy-a-layout-onto-a-client-machine.md
@@ -104,7 +104,7 @@ Some enterprises want to host the layout on an intranet location to better manag
 ## Prepare the client machines
 
 ### Permissions
-Make sure that either the user or system account that's running the installation has proper access to the network share that contains the layout. For more information, refer to the [troubleshoot network-related errors when you install or use Visual Studio](troubleshooting-network-related-errors-in-visual-studio.md) page.
+Make sure that either the user or system account that's running the installation has proper access to the network share that contains the layout. For more information, refer to the [troubleshoot network-related errors when you install or use Visual Studio](/troubleshoot/developer/visualstudio/installation/troubleshoot-network-related-errors) page.
 
 ### Install on a client that doesn't have internet access
 
@@ -138,7 +138,7 @@ We have other support options available, too. See our [Visual Studio Developer C
 
 - [Visual Studio administrator guide](visual-studio-administrator-guide.md)
 - [Update a network-based installation of Visual Studio](update-a-network-installation-of-visual-studio.md)
-- [Troubleshoot network-related errors when you install or use Visual Studio](troubleshooting-network-related-errors-in-visual-studio.md)
+- [Troubleshoot network-related errors when you install or use Visual Studio](/troubleshoot/developer/visualstudio/installation/troubleshoot-network-related-errors)
 - [Control updates to network-based Visual Studio deployments](controlling-updates-to-visual-studio-deployments.md)
 - [Configure policies for enterprise deployments of Visual Studio](configure-policies-for-enterprise-deployments.md) 
 - [Visual Studio product lifecycle and servicing](/visualstudio/productinfo/vs-servicing/)
diff --git a/docs/install/install-and-use-visual-studio-behind-a-firewall-or-proxy-server.md b/docs/install/install-and-use-visual-studio-behind-a-firewall-or-proxy-server.md
@@ -140,7 +140,7 @@ When you use Visual Studio or Azure Services behind a firewall or proxy server,
 
 ## Troubleshoot network-related errors
 
-Sometimes, you might run in to network- or proxy-related errors when you install or use Visual Studio behind a firewall or a proxy server. For more information about solutions for such error messages, see [Troubleshooting network-related errors](troubleshooting-network-related-errors-in-visual-studio.md).
+Sometimes, you might run in to network- or proxy-related errors when you install or use Visual Studio behind a firewall or a proxy server. For more information about solutions for such error messages, see [Troubleshooting network-related errors](/troubleshoot/developer/visualstudio/installation/troubleshoot-network-related-errors).
 
 ## Get support
 
@@ -156,6 +156,6 @@ Here are a few more support options:
 
 * [Connectivity requirements for Live Share](/visualstudio/liveshare/reference/connectivity/)
 * [Create and maintain a network installation of Visual Studio](create-a-network-installation-of-visual-studio.md)
-* [Troubleshoot network-related errors in Visual Studio](troubleshooting-network-related-errors-in-visual-studio.md)
+* [Troubleshoot network-related errors in Visual Studio](/troubleshoot/developer/visualstudio/installation/troubleshoot-network-related-errors)
 * [Visual Studio administrator guide](visual-studio-administrator-guide.md)
 * [Configure network settings for Copilot in Visual Studio](https://docs.github.com/en/copilot/configuring-github-copilot/configuring-network-settings-for-github-copilot?tool=visualstudio#configuring-proxy-settings-for-github-copilot)
diff --git a/docs/install/repair-visual-studio.md b/docs/install/repair-visual-studio.md
@@ -95,4 +95,4 @@ To repair your installation, follow these steps.
 - [Install Visual Studio](install-visual-studio.md)
 - [Update Visual Studio](update-visual-studio.md)
 - [Uninstall Visual Studio](uninstall-visual-studio.md)
-- [Troubleshooting Visual Studio installation and upgrade issues](troubleshooting-installation-issues.md)
+- [Troubleshooting Visual Studio installation and upgrade issues](/troubleshoot/developer/visualstudio/installation/troubleshoot-installation-issues)
diff --git a/docs/install/update-a-network-installation-of-visual-studio.md b/docs/install/update-a-network-installation-of-visual-studio.md
@@ -30,7 +30,7 @@ If your clients are [configured to acquire updates](update-visual-studio.md?view
 
 If your clients are [configured to acquire updates](update-visual-studio.md#configure-source-location-of-updates-1) from a layout, then the first step before updating the client is to make sure that the layout itself contains the updated version of Visual Studio. The IT administrator should either [update the existing layout with the latest product updates](create-a-network-installation-of-visual-studio.md#maintaining-your-layout) so that both new client installations or client updates can receive the updated version, or they can [create a whole new layout](create-a-network-installation-of-visual-studio.md) in a different layout directory that you can use to update the client machines. Best practice is to update the layouts on the second Tuesday of the month right after the security updates are released.
 
-Make sure that either the user or system account that's running the update has proper access to the network share or internal website that contains the layout. For more information, refer to [Troubleshoot network-related errors when you install or use Visual Studio](troubleshooting-network-related-errors-in-visual-studio.md#error-the-product-fails-to-install-or-update-because-network-share-permissions-arent-configured-correctly).
+Make sure that either the user or system account that's running the update has proper access to the network share or internal website that contains the layout. For more information, refer to [Troubleshoot network-related errors when you install or use Visual Studio](/troubleshoot/developer/visualstudio/installation/troubleshoot-network-related-errors#error-the-product-fails-to-install-or-update-because-network-share-permissions-arent-configured-correctly).
 
 ## Manually initiate the update on the client machine
 
@@ -148,7 +148,7 @@ We have other support options available, too. See our [Visual Studio Developer C
 
 * [Create and maintain a network layout](create-a-network-installation-of-visual-studio.md)
 * [Visual Studio administrator guide](visual-studio-administrator-guide.md)
-* [Troubleshoot network-related errors when you install or use Visual Studio](troubleshooting-network-related-errors-in-visual-studio.md)
+* [Troubleshoot network-related errors when you install or use Visual Studio](/troubleshoot/developer/visualstudio/installation/troubleshoot-network-related-errors)
 * [Use command-line parameters to install Visual Studio](use-command-line-parameters-to-install-visual-studio.md)
 * [Tools for detecting and managing Visual Studio instances](tools-for-managing-visual-studio-instances.md)
 * [Configure policies for enterprise deployments of Visual Studio](configure-policies-for-enterprise-deployments.md)
diff --git a/docs/install/visual-studio-administrator-guide.md b/docs/install/visual-studio-administrator-guide.md
@@ -125,7 +125,7 @@ The following resources help you keep your Visual Studio updated, current, and s
 
 - **[Tools for detecting, verifying, and managing Visual Studio instances](tools-for-managing-visual-studio-instances.md)** on client machines.
 
-- **[Troubleshoot Visual Studio installation and upgrade issues](troubleshooting-installation-issues.md)**. Get help when you're installing or updating Visual Studio, and learn how to report a problem if you're blocked. These tips include step-by-step instructions that should resolve most online or offline installation issues. 
+- **[Troubleshoot Visual Studio installation and upgrade issues](/troubleshoot/developer/visualstudio/installation/troubleshoot-installation-issues)**. Get help when you're installing or updating Visual Studio, and learn how to report a problem if you're blocked. These tips include step-by-step instructions that should resolve most online or offline installation issues. 
 
 - **[Repair Visual Studio](repair-visual-studio.md) to fix update issues**. Sometimes your Visual Studio installation becomes damaged or corrupted. A repair is useful for fixing install-time issues across all install operations, including updates. 
 
diff --git a/docs/snippets/cpp/VS_Snippets_Misc/astoria northwind service/astoriasnippetscs/properties/assemblyinfo.cs b/docs/snippets/cpp/VS_Snippets_Misc/astoria northwind service/astoriasnippetscs/properties/assemblyinfo.cs
@@ -15,7 +15,7 @@
 [assembly: AssemblyCulture("")]
 
 // Setting ComVisible to false makes the types in this assembly not visible 
-// to COM componenets.  If you need to access a type in this assembly from 
+// to COM components.  If you need to access a type in this assembly from 
 // COM, set the ComVisible attribute to true on that type.
 [assembly: ComVisible(false)]
 
diff --git a/docs/snippets/cpp/VS_Snippets_Misc/astoria northwind service/astoriasnippetsvb/properties/assemblyinfo.cs b/docs/snippets/cpp/VS_Snippets_Misc/astoria northwind service/astoriasnippetsvb/properties/assemblyinfo.cs
@@ -15,7 +15,7 @@
 [assembly: AssemblyCulture("")]
 
 // Setting ComVisible to false makes the types in this assembly not visible 
-// to COM componenets.  If you need to access a type in this assembly from 
+// to COM components.  If you need to access a type in this assembly from 
 // COM, set the ComVisible attribute to true on that type.
 [assembly: ComVisible(false)]
 
diff --git a/docs/snippets/csharp/VS_Snippets_VBCSharp/vbtddwalkthrough/cs/properties/assemblyinfo.cs b/docs/snippets/csharp/VS_Snippets_VBCSharp/vbtddwalkthrough/cs/properties/assemblyinfo.cs
@@ -15,7 +15,7 @@
 [assembly: AssemblyCulture("")]
 
 // Setting ComVisible to false makes the types in this assembly not visible 
-// to COM componenets.  If you need to access a type in this assembly from 
+// to COM components.  If you need to access a type in this assembly from 
 // COM, set the ComVisible attribute to true on that type.
 [assembly: ComVisible(false)]
 
diff --git a/docs/snippets/csharp/VS_Snippets_Winforms/ClickOnceAPI/CS/Properties/AssemblyInfo.cs b/docs/snippets/csharp/VS_Snippets_Winforms/ClickOnceAPI/CS/Properties/AssemblyInfo.cs
@@ -15,7 +15,7 @@
 [assembly: AssemblyCulture("")]
 
 // Setting ComVisible to false makes the types in this assembly not visible 
-// to COM componenets.  If you need to access a type in this assembly from 
+// to COM components.  If you need to access a type in this assembly from 
 // COM, set the ComVisible attribute to true on that type.
 [assembly: ComVisible(false)]
 
diff --git a/docs/snippets/csharp/VS_Snippets_Winforms/ClickOnceLibrary/CS/Properties/AssemblyInfo.cs b/docs/snippets/csharp/VS_Snippets_Winforms/ClickOnceLibrary/CS/Properties/AssemblyInfo.cs
@@ -15,7 +15,7 @@
 [assembly: AssemblyCulture("")]
 
 // Setting ComVisible to false makes the types in this assembly not visible 
-// to COM componenets.  If you need to access a type in this assembly from 
+// to COM components.  If you need to access a type in this assembly from 
 // COM, set the ComVisible attribute to true on that type.
 [assembly: ComVisible(false)]
 
diff --git a/docs/snippets/csharp/VS_Snippets_Winforms/ClickOnceOnDemand/CS/Properties/AssemblyInfo.cs b/docs/snippets/csharp/VS_Snippets_Winforms/ClickOnceOnDemand/CS/Properties/AssemblyInfo.cs
@@ -15,7 +15,7 @@
 [assembly: AssemblyCulture("")]
 
 // Setting ComVisible to false makes the types in this assembly not visible 
-// to COM componenets.  If you need to access a type in this assembly from 
+// to COM components.  If you need to access a type in this assembly from 
 // COM, set the ComVisible attribute to true on that type.
 [assembly: ComVisible(false)]
 
diff --git a/docs/snippets/csharp/VS_Snippets_Winforms/ClickOnceQueryString/CS/Properties/AssemblyInfo.cs b/docs/snippets/csharp/VS_Snippets_Winforms/ClickOnceQueryString/CS/Properties/AssemblyInfo.cs
@@ -10,12 +10,12 @@
 [assembly: AssemblyConfiguration("")]
 [assembly: AssemblyCompany("MS")]
 [assembly: AssemblyProduct("ClickOnceQueryString")]
-[assembly: AssemblyCopyright("Copyright � MS 2005")]
+[assembly: AssemblyCopyright("Copyright � MS 2005")]
 [assembly: AssemblyTrademark("")]
 [assembly: AssemblyCulture("")]
 
 // Setting ComVisible to false makes the types in this assembly not visible 
-// to COM componenets.  If you need to access a type in this assembly from 
+// to COM components.  If you need to access a type in this assembly from 
 // COM, set the ComVisible attribute to true on that type.
 [assembly: ComVisible(false)]
 
diff --git a/docs/vsto/codesnippet/CSharp/Trin_ServerDocument/Properties/AssemblyInfo.cs b/docs/vsto/codesnippet/CSharp/Trin_ServerDocument/Properties/AssemblyInfo.cs
@@ -10,12 +10,12 @@
 [assembly: AssemblyConfiguration("")]
 [assembly: AssemblyCompany("Microsoft")]
 [assembly: AssemblyProduct("Trin_ServerDocument")]
-[assembly: AssemblyCopyright("Copyright � Microsoft 2005")]
+[assembly: AssemblyCopyright("Copyright � Microsoft 2005")]
 [assembly: AssemblyTrademark("")]
 [assembly: AssemblyCulture("")]
 
 // Setting ComVisible to false makes the types in this assembly not visible 
-// to COM componenets.  If you need to access a type in this assembly from 
+// to COM components.  If you need to access a type in this assembly from 
 // COM, set the ComVisible attribute to true on that type.
 [assembly: ComVisible(false)]
 
diff --git a/docs/xaml-tools/debug-xaml-in-blend.md b/docs/xaml-tools/debug-xaml-in-blend.md
@@ -111,7 +111,7 @@ When XAML errors are detected, the design surface displays an alert that your pr
 
 You can open Blend projects in Visual Studio to more easily debug the code in your app. To open a Blend project in Visual Studio, right-click the project in the **Projects** panel, and then click **Edit in Visual Studio**. After you have finished your debugging session in Visual Studio, press Ctrl+Shift+S to save all your changes, and then switch back to Blend. You will be prompted to reload the project. Click **Yes to All** to continue working in Blend.
 
-For more information about debugging your app, see [Debug UWP apps in Visual Studio](../debugger/debugging-windows-store-and-windows-universal-apps.md).
+For more information about debugging your app, see [Debug UWP apps in Visual Studio](/windows/uwp/debug-test-perf/deploying-and-debugging-uwp-apps).
 
 ## Get help
 
diff --git a/docs/xaml-tools/xaml-hot-reload.md b/docs/xaml-tools/xaml-hot-reload.md
@@ -19,15 +19,15 @@ With XAML Hot Reload, you can incrementally build and test XAML code for your .N
 > [!TIP]
 > If you've arrived here by way of the XAML Hot Reload user interface (UI), welcome! You're in the right place to learn more about XAML Hot Reload.
 >
-> But, if you're here for help troubleshooting XAML Hot Reload, see [Troubleshooting XAML Hot Reload](xaml-hot-reload-troubleshooting.md) instead.
+> But, if you're here for help troubleshooting XAML Hot Reload, see [Troubleshooting XAML Hot Reload](/troubleshoot/developer/visualstudio/tools-utilities/xaml-hot-reload-troubleshooting) instead.
 
 ## Where to get XAML Hot Reload
 
 Visual Studio XAML Hot Reload is supported when you're running an application in **Visual Studio** -or- **Blend for Visual Studio** (if supported by the framework) with the debugger attached (**F5** or **Start debugging**).
 
 Starting in Visual Studio 2022 version 17.14 Preview 2, XAML Hot Reload and [XAML Live Preview](../xaml-tools/xaml-live-preview.md) are available at design-time and not just during a debugging session.
 
-You can't enable this experience by using [Attach to process](../debugger/attach-to-running-processes-with-the-visual-studio-debugger.md) unless you [manually set an environment variable](xaml-hot-reload-troubleshooting.md#verify-that-you-use-start-debugging-rather-than-attach-to-process).
+You can't enable this experience by using [Attach to process](../debugger/attach-to-running-processes-with-the-visual-studio-debugger.md) unless you [manually set an environment variable](/troubleshoot/developer/visualstudio/tools-utilities/xaml-hot-reload-troubleshooting#verify-that-you-use-start-debugging-rather-than-attach-to-process).
 
 ## Scenarios for XAML Hot Reload
 
@@ -56,7 +56,7 @@ The following animation shows an instance of using Live Visual Tree to open some
 
 ## Related content
 
-* [Troubleshooting XAML Hot Reload](xaml-hot-reload-troubleshooting.md)
+* [Troubleshooting XAML Hot Reload](/troubleshoot/developer/visualstudio/tools-utilities/xaml-hot-reload-troubleshooting)
 * [XAML Hot Reload for .NET MAUI](/dotnet/maui/xaml/hot-reload)
 * [Edit and Continue (Visual C#)](../debugger/edit-and-continue-visual-csharp.md)
 * [XAML data binding diagnostics](xaml-data-binding-diagnostics.md)
diff --git a/docs/xml-tools/how-to-use-xml-snippets.md b/docs/xml-tools/how-to-use-xml-snippets.md
@@ -101,7 +101,7 @@ Only the first instance of a given field is editable. When that field is highlig
 
 Pressing **Enter** or **Esc** cancels field editing and returns the editor to normal.
 
-The default colors for editable code snippet fields can be changed by modifying the **Code Snippet Field** setting in the **Fonts and Colors** pane of the **Options** dialog box. For more information, see [How to: Change fonts and colors in the editor](../ide/reference/how-to-change-fonts-and-colors-in-the-editor.md).
+The default colors for editable code snippet fields can be changed by modifying the **Code Snippet Field** setting in the **Fonts and Colors** pane of the **Options** dialog box. For more information, see [How to: Change fonts and colors in the editor](/visualstudio/ide/how-to-change-fonts-and-colors-in-visual-studio).
 
 ## Related content
 
diff --git a/subscriptions/vs-m365.md b/subscriptions/vs-m365.md
