sync

Author: Mikejo5000

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).
 

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 <xref:System.
 ## Output methods
  The <xref:System.Diagnostics.Trace> and <xref:System.Diagnostics.Debug> 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.
 
 - <xref:System.Diagnostics.Debug.Assert%2A?displayProperty=fullName> and <xref:System.Diagnostics.Trace.Assert%2A?displayProperty=fullName> 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).
 

docs/debugger/just-my-code.md

@@ -1,7 +1,7 @@
 ---
 title: Debug user code with Just My Code
 description: Just My Code is a debugging feature that automatically steps over calls to non-user code. Learn how to enable, disable, and use this feature.
-ms.date: 08/23/2024
+ms.date: 10/14/2024
 ms.topic: how-to
 author: mikejo5000
 ms.author: mikejo
@@ -123,7 +123,7 @@ If first chance exceptions are enabled for the exception, the calling user-code
 Starting in Visual Studio 2017 version 15.8, Just My Code for code stepping is also supported. This feature also requires use of the [/JMC (Just my code debugging)](/cpp/build/reference/jmc) compiler switch. The switch is enabled by default in C++ projects. For **Call Stack** window and call stack support in Just My Code, the /JMC switch isn't required.
 
 <a name="BKMK_CPP_User_and_non_user_code"></a>
-To be classified as user code, the PDB for the binary containing the user code must be loaded by the debugger (use the **Modules** window to check this).
+To be classified as user code, the PDB for the binary containing the user code must be loaded by the debugger (use the **Modules** window to check loading status).
 
 For call stack behavior, such as in the **Call Stack** window, Just My Code in C++ considers only these functions to be *non-user code*:
 
@@ -249,111 +249,6 @@ A *.natstepfilter* file is an XML file with this syntax:
 ## <a name="BKMK_JavaScript_Just_My_Code"></a> JavaScript Just My Code
 
 <a name="BKMK_JS_User_and_non_user_code"></a>
-JavaScript Just My Code controls stepping and call stack display by categorizing code in one of these classifications:
+For *.esproj* projects in Visual Studio 2022, Visual Studio Code uses a *launch.json* file to configure and customize the debugger. *launch.json* is a debugger configuration file.
 
-|Classification|Description|
-|-|-|
-|**MyCode**|User code that you own and control.|
-|**LibraryCode**|Non-user code from libraries that you use regularly and your app relies on to function correctly (for example, jQuery).|
-|**UnrelatedCode**|Non-user code in your app that you don't own and your app doesn't rely on to function correctly. For example, an advertising SDK that displays ads could be UnrelatedCode.|
-
-The JavaScript debugger classifies code as user or non-user in this order:
-
-1. The default classifications.
-   - Script executed by passing a string to the host-provided `eval` function is **MyCode**.
-   - Script executed by passing a string to the `Function` constructor is **LibraryCode**.
-   - Script in a framework reference, such as WinJS or the Azure SDK, is **LibraryCode**.
-   - Script executed by passing a string to the `setTimeout`, `setImmediate`, or `setInterval` functions is **UnrelatedCode**.
-
-2. Classifications in the *mycode.json* file of the current project.
-
-Each classification step overrides the previous steps.
-
-All other code is classified as **MyCode**.
-
-You can modify the default classifications, and classify specific files and URLs as user or non-user code, by adding a *.json* file named *mycode.json* to the root folder of a JavaScript project. See [Customize JavaScript Just My Code](#BKMK_JS_Customize_Just_My_Code).
-
-<a name="BKMK_JS_Stepping_behavior"></a>
-During JavaScript debugging:
-
-- If a function is non-user code, **Debug** > **Step Into** (or **F11**) behaves the same as **Debug** > **Step Over** (or **F10**).
-- If a step begins in non-user (**LibraryCode** or **UnrelatedCode**) code, stepping temporarily behaves as if Just My Code isn't enabled. When you step back to user code, Just My Code stepping is re-enabled.
-- When a user code step results in leaving the current execution context, the debugger stops at the next executed user code line. For example, if a callback executes in **LibraryCode** code, the debugger continues until the next line of user code executes.
-- **Step Out** (or **Shift**+**F11**) stops on the next line of user code.
-
-If there's no more user code, debugging continues until it ends, hits another breakpoint, or throws an error.
-
-Breakpoints set in code are always hit, but the code is classified.
-
-- If the `debugger` keyword occurs in **LibraryCode**, the debugger always breaks.
-- If the `debugger` keyword occurs in **UnrelatedCode**, the debugger doesn't stop.
-
-<a name="BKMK_JS_Exception_behavior"></a>
-If an unhandled exception occurs in **MyCode** or **LibraryCode** code, the debugger always breaks.
-
-If an unhandled exception occurs in **UnrelatedCode**, and **MyCode** or **LibraryCode** is on the call stack, the debugger breaks.
-
-If first-chance exceptions are enabled for the exception, and the exception occurs in **LibraryCode** or **UnrelatedCode**:
-
-- If the exception is handled, the debugger doesn't break.
-- If the exception isn't handled, the debugger breaks.
-
-### <a name="BKMK_JS_Customize_Just_My_Code"></a> Customize JavaScript Just My Code
-
-To categorize user and non-user code for a single JavaScript project, you can add a *.json* file named *mycode.json* to the root folder of the project.
-
-The *mycode.json* file doesn't need to list all key value pairs. The **MyCode**, **Libraries**, and **Unrelated** values can be empty arrays.
-
-*Mycode.json* files use this syntax:
-
-```json
-{
-    "Eval" : "Classification",
-    "Function" : "Classification",
-    "ScriptBlock" : "Classification",
-    "MyCode" : [
-        "UrlOrFileSpec",
-        . . .
-        "UrlOrFileSpec"
-    ],
-    "Libraries" : [
-        "UrlOrFileSpec",
-        . .
-        "UrlOrFileSpec"
-    ],
-    "Unrelated" : [
-        "UrlOrFileSpec",
-        . . .
-        "UrlOrFileSpec"
-    ]
-}
-
-```
-
-**Eval, Function, and ScriptBlock**
-
-The **Eval**, **Function**, and **ScriptBlock** key value pairs determine how dynamically generated code is classified:
-
-|Name|Description|
-|-|-|
-|**Eval**|Script that is executed by passing a string to the host-provided `eval` function. By default, Eval script is classified as **MyCode**.|
-|**Function**|Script that is executed by passing a string to the `Function` constructor. By default, Function script is classified as **LibraryCode**.|
-|**ScriptBlock**|Script that is executed by passing a string to the `setTimeout`, `setImmediate`, or `setInterval` functions. By default, ScriptBlock script is classified as **UnrelatedCode**.|
-
-You can change the value to one of these keywords:
-
-- `MyCode` classifies the script as **MyCode**.
-- `Library` classifies the script as **LibraryCode**.
-- `Unrelated` classifies the script as **UnrelatedCode**.
-
-**MyCode, Libraries, and Unrelated**
-
-The **MyCode**, **Libraries**, and **Unrelated** key value pairs specify the URLs or files that you want to include in a classification:
-
-|Name|Description|
-|-|-|
-|**MyCode**|An array of URLs or files that are classified as **MyCode**.|
-|**Libraries**|An array of URLs or files that are classified as **LibraryCode**.|
-|**Unrelated**|An array of URLs or files that are classified as **UnrelatedCode**.|
-
-The URL or file string can have one or more `*` characters, which match zero or more characters. `*` is the same as the regular expression `.*`.
+Visual Studio attaches the debugger only to user code. For *.esproj* projects, you can configure user code (that is, *Just My Code* settings) in Visual Studio using the `skipFiles` setting in *launch.json*. This setting works the same as the *launch.json* settings in VS Code. For more information about *skipFiles*, see [Skipping Uninteresting Code](https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_skipping-uninteresting-code).

docs/debugger/media/vs-2022/dbg-options-symbols.png

@@ -87,8 +87,8 @@ The debugger searches for symbol files in the following locations:
 
      **Third-party symbol servers**: Third-party providers of Windows applications and libraries can provide access to symbol server on the internet.
 
-     > [!WARNING]
-     > If you use a symbol server other than the public Microsoft Symbol Servers, make sure that the symbol server and its path are trustworthy. Because symbol files can contain arbitrary executable code, you can be exposed to security threats.
+  > [!WARNING]
+  > If you use a symbol server other than the public Microsoft Symbol Servers, make sure that the symbol server and its path are trustworthy. Because symbol files can contain arbitrary executable code, you can be exposed to security threats.
 
 ## Configure location of symbol files and loading options
 
@@ -103,6 +103,11 @@ On the **Tools** > **Options** > **Debugging** > **Symbols** page, you can:
 
 **To specify symbol locations and loading options:**
 
+::: moniker range="= vs-2022"
+  > [!NOTE]
+  > These options were updated in Visual Studio 2022 Version 17.12 Preview 1.
+::: moniker-end
+
 1. In Visual Studio, open **Tools** > **Options** > **Debugging** > **Symbols** (or **Debug** > **Options** > **Symbols**).
 
 2. Under **Symbol file (.pdb) locations**,
@@ -112,15 +117,15 @@ On the **Tools** > **Options** > **Debugging** > **Symbols** page, you can:
      1. Select the **+** symbol in the toolbar.
      1. Type the URL (http), network share, or local path of the symbol server or symbol location in the text field. Statement completion helps you find the correct format.
 
-     ::: moniker range=">= vs-2022"
+    ::: moniker range=">= vs-2022"
      ![Tools - Options - Debugging - Symbols page](media/vs-2022/dbg-options-symbols.png "Tools - Options - Debugging - Symbols page")
-     ::: moniker-end
-     ::: moniker range="<= vs-2019"
+    ::: moniker-end
+    ::: moniker range="<= vs-2019"
      ![Tools &#45; Options &#45; Debugging &#45; Symbols page](media/dbg-options-symbols.gif "Tools &#45; Options &#45; Debugging &#45; Symbols page")
-     ::: moniker-end
+    ::: moniker-end
 
-     >[!NOTE]
-     >Only the specified folder is searched. You must add entries for any subfolders that you want to search.
+   > [!NOTE]
+   > Only the specified folder is searched. You must add entries for any subfolders that you want to search.
 
    - To add a new Azure DevOps Symbol Server location:
 
@@ -135,20 +140,79 @@ On the **Tools** > **Options** > **Debugging** > **Symbols** page, you can:
 
 3. (Optional) To improve symbol loading performance, under **Cache symbols in this directory**, type a local folder path that symbol servers can copy symbols to.
 
-   > [!NOTE]
-   > Do not place the local symbol cache in a protected folder, like C:\Windows or a subfolder. Use a read-write folder instead.
+  > [!NOTE]
+  > Do not place the local symbol cache in a protected folder, like C:\Windows or a subfolder. Use a read-write folder instead.
 
-   > [!NOTE]
-   > For C++ projects, if you have the `_NT_SYMBOL_PATH` environment variable set, it will override the value set under **Cache symbols in this directory**.
+  > [!NOTE]
+  > If you have the `_NT_SYMBOL_PATH` environment variable set, it overrides the value set under **Cache symbols in this directory**.
 
 4. Specify the modules that you want the debugger to load from the **Symbol file (.pdb) locations** when it starts.
 
+   ::: moniker range=">= vs-2022"
+
+   - Select **Automatically choose what module symbols to search for** (recommended) to allow
+   Visual studio to decide what symbols to search for and load. By default, Visual Studio
+   automatically loads symbols that were built by your opened solution, and loads any
+   additional symbols that are needed to perform common debugging operations. This reduces
+   the number of files that must be searched for and loaded by Visual Studio, which 
+   improves debugger performance. You can force additional symbols to load by clicking the
+   **Specify module filters** link.
+
+   - Select **Search for all module symbols unless excluded** to force Visual Studio to
+   load all symbols in your debugged process. This is not recommended because it may
+   slow down your debugging experience. If you select this option, you can force
+   Visual Studio to ignore certain symbols by clicking the **Specify module filters**
+   link.
+
+   ::: moniker-end
+   ::: moniker range="<= vs-2019"
+
    - Select **Load all modules, unless excluded** (the default) to load all the symbols for all modules in the symbol file location, except modules you specifically exclude. To exclude certain modules, select **Specify excluded modules**, select the **+** icon, type the names of the modules to exclude, and select **OK**.
 
    - To load only modules you specify from the symbol file locations, select **Load only specified modules**. Select **Specify included modules**, select the **+** icon, type the names of the modules to include, and then select **OK**. The symbol files for other modules are not loaded.
+   ::: moniker-end
 
 5. Select **OK**.
 
+::: moniker range=">= vs-2022"
+
+### Specify module filters
+Both the **Automatically choose what module symbols to search for** and **Search for all
+module symbols unless excluded** options allow you to have more fine control over what symbols
+are searched for while debugging. Choose **Specify module filters** to fine-tune your experience.
+
+By default, you see the following dialog when **Automatically choose what module symbols to search for** is selected:
+
+![Screenshot of specifying module filters.](media/vs-2022/specify-include-list.png)
+
+You can add a module to the filter by using the '+' icon. Module filters support simple wild-card
+matching. A '\*' matches any group of characters. For example '\*myproduct\*' will match files such
+as 'myproduct.utilities.dll' and 'entrypoint.myproduct.exe', among others.
+
+There are several additional options to further customize your experience:
+
+- **Always load symbols located next to modules** instructs visual studio to load pdb files that
+are stored in the file system beside their corresponding .dll or .exe files. This can be helpful,
+for example, when attempting to debug a deployed web app.
+
+- **Automatically load additional symbols when needed** instructs Visual Studio to search for
+symbols to perform common debug actions, such as stepping, even if the module that you will be
+stepping to is not in your project or in the modules filter. The way that searching is determined
+might be affected by your [Just My Code](just-my-code.md) settings.
+
+If you have selected **Search for all module symbols unless excluded**, then the module filter
+dialog looks like this:
+
+![Screenshot of specifying excluded modules.](media/vs-2022/specify-exclude-list.png)
+
+In this dialog, you can choose what modules you *do not* want Visual Studio to load symbols for.
+In this scenario, Visual Studio attempts to load symbols for every module in your debugged
+proces (including modules by third parties), unless you add a matching filter to exclude them.
+The only other way that this behavior will be modified is by your [Just My Code](just-my-code.md)
+settings.
+
+::: moniker-end
+
 ## Other symbol options for debugging
 
 You can select additional symbol options in **Tools** > **Options** > **Debugging** > **General** (or **Debug** > **Options** > **General**):
@@ -169,10 +233,10 @@ You can select additional symbol options in **Tools** > **Options** > **Debuggin
 
   You can limit the commands that *srcsrv.dll* can execute from the app's *.pdb* file by listing the allowed commands in a file named *srcsrv.ini*. Place the *srcsrv.ini* file in the same folder as *srcsrv.dll* and *devenv.exe*.
 
-  >[!IMPORTANT]
-  >Arbitrary commands can be embedded in an app's *.pdb* file, so make sure to put only the commands you want to execute into a *srcsrv.ini* file. Any attempt to execute a command not in the *srcsvr.ini* file will cause a confirmation dialog box to appear. For more information, see [Security Warning: Debugger Must Execute Untrusted Command](../debugger/security-warning-debugger-must-execute-untrusted-command.md).
+  > [!IMPORTANT]
+  > Arbitrary commands can be embedded in an app's *.pdb* file, so make sure to put only the commands you want to execute into a *srcsrv.ini* file. Any attempt to execute a command not in the *srcsvr.ini* file will cause a confirmation dialog box to appear. For more information, see [Security Warning: Debugger Must Execute Untrusted Command](../debugger/security-warning-debugger-must-execute-untrusted-command.md).
   >
-  >No validation is done on command parameters, so be careful with trusted commands. For example, if you listed *cmd.exe* in your *srcsrv.ini*, a malicious user might specify parameters on *cmd.exe* that would make it dangerous.
+  > No validation is performed on command parameters, so be careful with trusted commands. For example, if you listed *cmd.exe* in your *srcsrv.ini*, a malicious user might specify parameters on *cmd.exe* that would make it dangerous.
 
   Select this item and the child items you want. **Allow source server for partial trust assemblies (Managed only)** and **Always run untrusted source server commands without prompting** can increase the security risks.
 

docs/debugger/media/vs-2022/specify-exclude-list.png

@@ -94,6 +94,9 @@
     "externalReference": [],
     "globalMetadata": {
       "feedback_system": "Standard",
+      "feedback_help_link_url": "https://developercommunity.microsoft.com/VisualStudio",
+      "feedback_help_link_type": "ask-the-community",      
+      "feedback_product_url": "https://developercommunity.visualstudio.com/VisualStudio/suggest",
       "breadcrumb_path": "/visualstudio/_breadcrumb/toc.json",
       "manager": "jmartens",
       "audience": "developer",