Merge pull request #10295 from MicrosoftDocs/main638551335396014993sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -594,6 +594,41 @@
       "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/data-tools/walkthrough-creating-a-wcf-data-service-with-wpf-and-entity-framework",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/deployment/how-to-enable-autostart-for-cd-installations.md",
+      "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/deployment/how-to-specify-a-start-menu-name-for-a-clickonce-application.md",
+      "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/deployment/how-to-change-the-publish-language-for-a-clickonce-application.md",
+      "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/deployment/how-to-specify-a-support-url-for-individual-prerequisites-in-a-clickonce-deployment.md",
+      "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/deployment/how-to-specify-a-link-for-technical-support.md",
+      "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/deployment/how-to-customize-the-default-web-page-for-a-clickonce-application.md",
+      "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/deployment/how-to-specify-a-publish-page-for-a-clickonce-application.md",
+      "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/deployment/how-to-automatically-increment-the-clickonce-publish-version.md",
       "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",

docs/debugger/media/vs-2022/dbg-dump-summary-page.png

@@ -1,7 +1,7 @@
 ---
 title: "Navigate code with the debugger"
 description: "Learn how to use the Visual Studio debugger to troubleshoot your code. Topics include entering break mode, stepping through code, and running to a target."
-ms.date: 06/16/2023
+ms.date: 06/27/2024
 ms.topic: how-to
 f1_keywords: 
   - vs.debug.execution

docs/debugger/navigating-through-code-with-the-debugger.md

@@ -1,7 +1,7 @@
 ---
 title: "Use dump files in the debugger"
 description: A dump file is a snapshot of an executing app and loaded modules. Consider creating a dump file for situations where you don't have debug access to the app.
-ms.date: "06/26/2023"
+ms.date: "06/27/2024"
 ms.topic: "conceptual"
 f1_keywords:
   - "vs.debug.crashdump"
@@ -74,11 +74,18 @@ With [Just-In-Time Debugging](../debugger/just-in-time-debugging-in-visual-studi
 
    The **Minidump File Summary** window shows summary and module information for the dump file, and actions you can take.
 
+   ::: moniker range=">=vs-2022"
+   :::image type="content" source="../debugger/media/vs-2022/dbg-dump-summary-page.png" alt-text="Screenshot showing Minidump summary page.":::
+   ::: moniker-end
+   ::: moniker range="vs-2019"
    :::image type="content" source="../debugger/media/dbg_dump_summarypage.png" alt-text="Screenshot showing Minidump summary page.":::
+   ::: moniker-end
 
 1. Under **Actions**:
+  
    - To set symbol loading locations, select **Set symbol paths**.
-   - To start debugging, select **Debug with Managed Only**, **Debug with Native Only**, **Debug with Mixed**, or **Debug with Managed Memory**.
+   - To start debugging, select **Debug with Managed Only**, **Debug with Mixed**, **Debug with Native Only**, or **Debug Managed Memory**. To analyze managed memory, see [Managed type reports](../profiling/memory-usage-without-debugging2.md#managed-types-reports).
+   - To get memory analysis on the dump, select **Run Diagnostic Analysis** and see [Debug a managed memory dump with .NET Diagnostic Analyzers](../debugger/how-to-debug-managed-memory-dump.md).
 
 ## <a name="BKMK_Find_binaries__symbol___pdb__files__and_source_files"></a> Find .exe, .pdb, and source files