Skip to content

Commit 410f08a

Browse files
Learn Build Service GitHub AppLearn Build Service GitHub App
authored andcommitted
Merging changes synced from https://github.com/MicrosoftDocs/visualstudio-docs-pr (branch live)
2 parents 43400d3 + 7291bbb commit 410f08a

File tree

3 files changed

+8
-6
lines changed

3 files changed

+8
-6
lines changed

docs/debugger/debug-using-the-just-in-time-debugger.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Debug using the Just-In-Time Debugger
33
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.
4-
ms.date: 10/09/2024
4+
ms.date: 01/29/2025
55
ms.topic: how-to
66
helpviewer_keywords:
77
- debugging [Visual Studio], Just-In-Time
@@ -52,18 +52,18 @@ Just-In-Time debugging might still be enabled even if Visual Studio is no longer
5252

5353
2. In the **Registry Editor** window, locate and delete the following registry entries if they exist:
5454

55-
- **HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\\.NETFramework\DbgManagedDebugger**
56-
5755
- **HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger**
5856

57+
- **HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\\.NETFramework\DbgManagedDebugger**
58+
5959
:::image type="content" source="../debugger/media/dbg-jit-registry.png" alt-text="JIT registry key" border="true":::
6060

6161
3. Also delete the following registry entries if they exist:
6262

63-
- **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\\.NETFramework\DbgManagedDebugger**
64-
6563
- **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger**
6664

65+
- **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\\.NETFramework\DbgManagedDebugger**
66+
6767
Make sure not to delete or change any other registry keys.
6868

6969
4. Close the **Registry Editor** window.
-28.4 KB
Loading

docs/install/command-line-parameter-examples.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Command-line parameter examples for installation
33
description: Customize command-line parameter examples to create your own installation of Visual Studio by setting parameters, such as installPath, wait, all, remove, and more.
4-
ms.date: 10/14/2024
4+
ms.date: 1/31/2025
55
ms.topic: conceptual
66
author: anandmeg
77
ms.author: meghaanand
@@ -18,6 +18,8 @@ All commands require administrative elevation, and a User Account Control prompt
1818

1919
You can use the `^` character at the end of a command line to concatenate multiple lines into a single command. Alternatively, you can place these lines together onto a single row. In PowerShell, the equivalent is the backtick (`` ` ``) character.
2020

21+
To execute commands in a non-interactive manner, you can use`--passive` or `--quiet`. For more information on these parameters, see the [commands and command-line paremeters](use-command-line-parameters-to-install-visual-studio.md#install-update-modify-repair-uninstall-and-export-commands-and-command-line-parameters) page.
22+
2123
For lists of the workloads and components that you can install by using the command line, see the [Visual Studio workload and component IDs](workload-and-component-ids.md) page.
2224

2325
## Install using --installPath and --add alongside the bootstrapper

0 commit comments

Comments
 (0)