Merge pull request #14335 from wiktork/main

Document Snappoint debugging deprecation

Author: JamesJBarnett

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)