Merge pull request #11065 from MicrosoftDocs/main638942655456506056sync_temp

Repo sync for protected branch

Author: v-regandowner

.openpublishing.redirection.json

@@ -5,6 +5,21 @@
       "redirect_url": "/visualstudio/msbuild/msbuild",
       "redirect_document_id": false
     },
+    {
+       "source_path": "docs/ide/reference/options-text-editor-xaml-formatting.md",
+       "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/ide/reference/options-text-editor-xaml-formatting",
+       "redirect_document_id": false
+    },
+    {
+       "source_path": "docs/ide/reference/options-text-editor-xaml-miscellaneous.md",
+       "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/ide/reference/options-text-editor-xaml-miscellaneous",
+       "redirect_document_id": false
+    },
+    {
+       "source_path": "docs/ide/reference/call-hierarchy.md",
+       "redirect_url": "/visualstudio/ide/call-hierarchy",
+       "redirect_document_id": false
+    },
     {
        "source_path": "docs/ide/reference/import-and-export-settings-environment-options-dialog-box.md",
        "redirect_url": "/visualstudio/ide/personalizing-the-visual-studio-ide",

docs/debugger/configure-the-windows-firewall-for-remote-debugging.md

@@ -46,6 +46,15 @@ To open a port using PowerShell:
 
 For Windows Firewall, you can use PowerShell commands such as [New-NetFirewallRule](/powershell/module/netsecurity/new-netfirewallrule).
 
+::: moniker range="visualstudio"
+The following example opens port 4026 for the remote debugger on the remote computer. The port and path you need to use might be different.
+
+```ps
+New-NetFirewallRule -DisplayName "msvsmon" -Direction Inbound -Program "Program Files\Microsoft Visual Studio\18\Enterprise\Common7\IDE\Remote Debugger\x64\msvsmon.exe" -LocalPort 4026 -Protocol TCP -Authentication Required -Action Allow
+```
+
+::: moniker-end
+
 ::: moniker range="vs-2022"
 The following example opens port 4026 for the remote debugger on the remote computer. The port and path you need to use might be different.
 

docs/debugger/debug-live-azure-applications.md

@@ -14,6 +14,8 @@ ms.custom: sfi-image-nochange
 ---
 # Debug live ASP.NET Azure apps using the Snapshot Debugger
 
+[!INCLUDE [debug-live-deprecation](includes/debug-live-deprecation.md)]
+
 The Snapshot Debugger takes a snapshot of your in-production apps when code that you're interested in executes. To instruct the debugger to take a snapshot, you set snappoints and logpoints in your code. The debugger lets you see exactly what went wrong, without impacting traffic of your production application. The Snapshot Debugger can help you dramatically reduce the time it takes to resolve issues that occur in production environments.
 
 Snappoints and logpoints are similar to breakpoints, but unlike breakpoints, snappoints don't halt the application when hit. Typically, capturing a snapshot at a snappoint takes 10-20 milliseconds.

docs/debugger/debug-live-azure-kubernetes.md

@@ -12,6 +12,8 @@ monikerRange: '>= vs-2019'
 ---
 # Debug live ASP.NET Azure Kubernetes Services using the Snapshot Debugger
 
+[!INCLUDE [debug-live-deprecation](includes/debug-live-deprecation.md)]
+
 The Snapshot Debugger takes a snapshot of your in-production apps when code that you're interested in executes. To instruct the debugger to take a snapshot, you set snappoints and logpoints in your code. The debugger lets you see exactly what went wrong, without impacting traffic of your production application. The Snapshot Debugger can help you dramatically reduce the time it takes to resolve issues that occur in production environments.
 
 Snappoints and logpoints are similar to breakpoints, but unlike breakpoints, snappoints don't halt the application when hit. Typically, capturing a snapshot at a snappoint takes 10-20 milliseconds.

docs/debugger/debug-live-azure-virtual-machines-time-travel-debugging.md

@@ -12,6 +12,8 @@ monikerRange: '>= vs-2019'
 ---
 # Use time travel debugging to record and replay ASP.NET apps on Azure VMs
 
+[!INCLUDE [debug-live-deprecation](includes/debug-live-deprecation.md)]
+
 Time travel debugging in Visual Studio Enterprise can record a web app running on an Azure virtual machine (VM), and then accurately reconstruct and replay the execution path. Time Travel Debugging (TTD) was added to Visual Studio 2019 Enterprise as a preview feature, and is now integrated into the Visual Studio Snapshot Debugger.
 
 Time travel debugging lets you rewind and replay each line of code as many times as you want. This procedure can help you isolate and identify problems that might occur only in production environments.

docs/debugger/debug-live-azure-virtual-machines.md

@@ -12,6 +12,8 @@ monikerRange: '>= vs-2019'
 ---
 # Debug live ASP.NET apps on Azure virtual machines and Azure virtual machine scale sets using the Snapshot Debugger
 
+[!INCLUDE [debug-live-deprecation](includes/debug-live-deprecation.md)]
+
 The Snapshot Debugger takes a snapshot of your in-production apps when code that you're interested in executes. To instruct the debugger to take a snapshot, you set snappoints and logpoints in your code. The debugger lets you see exactly what went wrong, without impacting traffic of your production application. The Snapshot Debugger can help you dramatically reduce the time it takes to resolve issues that occur in production environments.
 
 Snappoints and logpoints are similar to breakpoints, but unlike breakpoints, snappoints don't halt the application when hit. Typically, capturing a snapshot at a snappoint takes 10-20 milliseconds.

docs/debugger/includes/debug-live-deprecation.md

@@ -0,0 +1,9 @@
+---
+ms.topic: include
+---
+> [!NOTE]
+> Snapshot debugging has been deprecated and will no longer be available in the latest versions of Visual Studio 2022 and later versions. While there's no exact replacement, there are other tools that can provide helpful diagnostics:
+>
+> - [dotnet-monitor](/dotnet/core/diagnostics/dotnet-monitor)
+> - [Time Travel Debugging](/windows-hardware/drivers/debuggercmds/time-travel-debugging-overview)
+> - [ProcDump](/sysinternals/downloads/procdump)

docs/debugger/includes/remote-debugger-download-cpp.md

@@ -12,7 +12,12 @@
 
 On the remote device or server that you want to debug on, rather than the Visual Studio machine, download and install the correct version of the remote tools from the links in the following table.
 
-- Download the most recent remote tools for your version of Visual Studio. The latest remote tools version is compatible with earlier Visual Studio versions, but earlier remote tools versions aren't compatible with later Visual Studio versions. (For example, if you're using Visual Studio 2019, download the latest update of the remote tools for Visual Studio 2019. In this scenario, don't download the remote tools for Visual Studio 2022.)
+::: moniker range=">=visualstudio"
+- Download the most recent update of the remote tools for your version of Visual Studio. Remote tools for Visual Studio 2022 and 2026 can be used with either version of Visual Studio. However, remote tools versions that are earlier than Visual Studio 2022 aren't compatible with later Visual Studio versions. (For example, if you're using Visual Studio 2019, download the latest update of the remote tools for Visual Studio 2019. In this scenario, don't download the remote tools for Visual Studio 2022.)
+::: moniker-end
+::: moniker range="vs-2022"
+- Download the most recent update of the remote tools for your version of Visual Studio. Earlier remote tools versions aren't compatible with later Visual Studio versions. (For example, if you're using Visual Studio 2019, download the latest update of the remote tools for Visual Studio 2019. In this scenario, don't download the remote tools for Visual Studio 2022.)
+::: moniker-end
 - Download the remote tools with the same architecture as the machine you're installing them on. For example, if you want to debug a 32-bit app on a remote computer running a 64-bit operating system, install the 64-bit remote tools.
 - If you're remote debugging an ARM64EC application on an ARM64 device, install the ARM64 remote tools, and then launch the x64 remote debugger that gets installed with those tools. This can be found under: *Program Files (x86)\Microsoft Visual Studio\<version>\Common7\IDE\Remote Debugger\x64*.
 

docs/debugger/includes/remote-debugger-download.md

@@ -12,9 +12,14 @@ title: Remote debugger download
 
 On the remote device or server that you want to debug on, rather than the Visual Studio machine, download and install the correct version of the remote tools from the links in the following table.
 
+::: moniker range=">=visualstudio"
+- Download the most recent update of the remote tools for your version of Visual Studio. Remote tools for Visual Studio 2022 and 2026 can be used with either version of Visual Studio. However, remote tools versions that are earlier than Visual Studio 2022 aren't compatible with later Visual Studio versions. (For example, if you're using Visual Studio 2019, download the latest update of the remote tools for Visual Studio 2019. In this scenario, don't download the remote tools for Visual Studio 2022.)
+::: moniker-end
+::: moniker range="vs-2022"
 - Download the most recent update of the remote tools for your version of Visual Studio. Earlier remote tools versions aren't compatible with later Visual Studio versions. (For example, if you're using Visual Studio 2019, download the latest update of the remote tools for Visual Studio 2019. In this scenario, don't download the remote tools for Visual Studio 2022.)
+::: moniker-end
 - Download the remote tools with the same architecture as the machine you're installing them on. For example, if you want to debug x86 applications on a remote computer running an x64 operating system, install the x64 remote tools. To debug x86, ARM, or x64 applications on an ARM64 operating system, install the ARM64 remote tools.
-   
+
 ::: moniker range=">=vs-2022"
 
 |Version|Link|Notes|

docs/debugger/using-the-intellitrace-stand-alone-collector.md

@@ -71,8 +71,12 @@ The **IntelliTrace stand-alone collector** lets you collect IntelliTrace diagnos
 2. Get the collector from the Visual Studio installation folder.
 
    1. Copy IntelliTraceCollection.cab from the folder where the collector is installed, for example:
-
+        ::: moniker range=">=visualstudio"
+        **..\Microsoft Visual Studio\18\Enterprise\Common7\IDE\CommonExtensions\Microsoft\IntelliTrace**
+        ::: moniker-end
+        ::: moniker range="<=vs-2022"
         **..\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\CommonExtensions\Microsoft\IntelliTrace**
+        ::: moniker-end
 
         or, for previous versions of Visual Studio: