From 6b28720aed1483a9c4c96a569f24d8c12560319a Mon Sep 17 00:00:00 2001 From: "Mike Jones (DOCS)" Date: Thu, 3 Oct 2024 16:27:09 -0700 Subject: [PATCH 1/2] sync --- docs/debugger/diagnostic-messages-in-the-output-window.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/debugger/diagnostic-messages-in-the-output-window.md b/docs/debugger/diagnostic-messages-in-the-output-window.md index 2f75e33d505..d80947d8256 100644 --- a/docs/debugger/diagnostic-messages-in-the-output-window.md +++ b/docs/debugger/diagnostic-messages-in-the-output-window.md @@ -28,7 +28,7 @@ You can write run-time messages to the **Output** window using the and classes provide the following output methods: -- Various [Write](/dotnet/api/system.diagnostics.debug#methods) methods, which output information without breaking execution. These methods replace the `Debug.Print` method used in previous versions of Visual Basic. +- Various [Write](/dotnet/api/system.diagnostics.debug#methods) methods, which output information without breaking execution. These methods replace the `Debug.Print` method used in older versions of Visual Basic. - and methods, which break execution and output information if a specified condition fails. By default, the `Assert` method displays the information in a dialog box. For more information, see [Assertions in managed code](../debugger/assertions-in-managed-code.md). From b5e7a1816c687d953e7dad8109089d4380a78287 Mon Sep 17 00:00:00 2001 From: "Mike Jones (DOCS)" Date: Wed, 9 Oct 2024 09:31:47 -0700 Subject: [PATCH 2/2] Update registry key information for JIT debugging --- .../debug-using-the-just-in-time-debugger.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/debugger/debug-using-the-just-in-time-debugger.md b/docs/debugger/debug-using-the-just-in-time-debugger.md index 9a041b92245..d01b186d0d9 100644 --- a/docs/debugger/debug-using-the-just-in-time-debugger.md +++ b/docs/debugger/debug-using-the-just-in-time-debugger.md @@ -1,7 +1,7 @@ --- title: Debug using the Just-In-Time Debugger description: Debug using the Just-In-Time Debugger in Visual Studio. Just-In-Time debugging can launch Visual Studio automatically when an app returns errors or crashes. -ms.date: 11/29/2023 +ms.date: 10/09/2024 ms.topic: how-to helpviewer_keywords: - debugging [Visual Studio], Just-In-Time @@ -153,17 +153,17 @@ If Just-In-Time debugging doesn't start when an app crashes, even though it's en The fix is to add a **DWORD Value** of **Auto**, with **Value data** of **1**, to the following registry keys: - - **HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug** + - **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug** - - (For 32-bit machines) **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug** + - (For 32-bit apps on 64-bit machines) **HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug** - Windows Error Reporting could be taking over the error handling on your computer. To fix this issue, use Registry Editor to add a **DWORD Value** of **Disabled**, with **Value data** of **1**, to the following registry keys: - - - **HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\Windows\Windows Error Reporting** - - (For 32-bit machines) **HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Error Reporting** + - **HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Error Reporting** + + - (For 32-bit apps on 64-bit machines) **HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\Windows\Windows Error Reporting** For more information, see [.WER settings](/windows/desktop/wer/wer-settings).