Merge pull request #13832 from Mikejo5000/mikejo-br26

Update article on use of Modules window

Author: JamesJBarnett

docs/debugger/debug-64-bit-applications.md

@@ -1,7 +1,7 @@
 ---
 title: Debug and troubleshoot 64-Bit applications
 description: Learn how to debug a 64-bit application with Visual Studio. There are tips for troubleshooting unexpected debugging delays.
-ms.date: 11/04/2016
+ms.date: 04/16/2025
 ms.topic: how-to
 dev_langs:
   - CSharp
@@ -24,9 +24,9 @@ You can debug a 64-bit application that is running on the local computer or on a
 
 To debug a 64-bit application that is running on a remote computer, see [Remote Debugging](../debugger/remote-debugging.md).
 
-To debug 64-bit applications locally, Visual Studio uses a 64-bit worker process (msvsmon.exe) to perform the low-level operations that cannot be done inside of the 32-bit Visual Studio process.
+To debug 64-bit applications locally, Visual Studio uses a 64-bit worker process (msvsmon.exe) to perform the low-level operations that can't be done inside of the 32-bit Visual Studio process.
 
-Mixed-mode debugging is not supported for 64-bit processes that use .NET Framework version 3.5 or earlier.
+Mixed-mode debugging isn't supported for 64-bit processes that use .NET Framework version 3.5 or earlier.
 
 ## Debug a 64-bit Application
 
@@ -46,9 +46,9 @@ You might see an error: "A 64-bit debugging operation is taking longer than expe
 
 There are two main causes for this error:
 
-- You have networking security software installed on your computer that has caused the networking stack to be unreliable, and it has dropped packets going over `localhost`. Try disabling all network security software and see whether this resolves it. If so, report to your network security software vendor that the software is interfering with `localhost` traffic. This should not occur with Visual Studio 2019 and later, because those versions don't use sockets for this communication.
+- You have networking security software installed on your computer that has caused the networking stack to be unreliable, and it has dropped packets going over `localhost`. Try disabling all network security software and see whether this resolves it. If so, report to your network security software vendor that the software is interfering with `localhost` traffic. This shouldn't occur with Visual Studio 2019 and later, because those versions don't use sockets for this communication.
 
-- You are running into an issue where Visual Studio becomes unresponsive, or other performance problem. If the problem happens regularly, you can collect dumps of Visual Studio (devenv.exe) and the worker process (msvsmon.exe) and send them to Microsoft. For information about reporting a problem, see [How to Report a Problem with Visual Studio](../ide/how-to-report-a-problem-with-visual-studio.md).
+- You're running into an issue where Visual Studio becomes unresponsive, or other performance problem. If the problem happens regularly, you can collect dumps of Visual Studio (devenv.exe) and the worker process (msvsmon.exe) and send them to Microsoft. For information about reporting a problem, see [How to Report a Problem with Visual Studio](../ide/how-to-report-a-problem-with-visual-studio.md).
 
 ## Related content
 

docs/debugger/get-started-debugging-multithreaded-apps.md

@@ -1,7 +1,7 @@
 ---
 title: Learn to debug multithreaded applications
 description: Debug multithreaded applications by using the Parallel Stacks and Parallel Watch windows in the Visual Studio integrated development environment (IDE).
-ms.date: 10/19/2023
+ms.date: 04/16/2025
 ms.topic: how-to
 dev_langs: 
   - CSharp

docs/debugger/how-to-use-the-modules-window.md

@@ -2,7 +2,7 @@
 title: View DLLs and executables in Visual Studio
 description: View DLLs and executables (.exe files) that your app uses in the Modules window during a debugging session in Visual Studio.
 titleSuffix: Visual Studio Modules window
-ms.date: 11/04/2018
+ms.date: 04/16/2025
 ms.topic: how-to
 f1_keywords: 
   - vs.debug.modules
@@ -31,15 +31,17 @@ During Visual Studio debugging, the **Modules** window lists and shows informati
 > [!NOTE]
 > The Modules window is not available for SQL or script debugging.
 
-## Use the Modules window
+## View modules
 
 To open the Modules window, while you're debugging, select **Debug** > **Windows** > **Modules** (or press **Ctrl + Alt + U**).
 
 By default, the **Modules** window sorts modules by load order. To sort by any window column, select the header at the top of the column.
 
 ## Load symbols
 
-The **Symbol Status** column in the **Modules** window shows which modules have debugging symbols loaded. If the status is **Skipped loading symbols**, **Cannot find or open the PDB file**, or **Loading disabled by include/exclude setting**, you can load symbols manually. For more information about loading and using symbols, see [Specify symbol (.pdb) and source files](../debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md).
+The **Symbol Status** column in the **Modules** window shows which modules have debugging symbols loaded. If the status is **Skipped loading symbols**, **Cannot find or open the PDB file**, or **Loading disabled by include/exclude setting**, you can load symbols manually.
+
+- For more information about loading and using symbols, see [Specify symbol (.pdb) and source files](../debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md).
 
 **To load symbols manually:**
 
@@ -49,6 +51,12 @@ The **Symbol Status** column in the **Modules** window shows which modules have
 
    - Select **Load Symbols** to load the symbols manually.
 
+   - For .NET code, you can choose **Decompile Source to Symbol File** and then follow instructions in [Generate and embed sources for an assembly](../debugger/decompilation.md#generate-and-embed-sources-for-an-assembly).
+   
+     ::: moniker range=">=vs-2022"
+     Starting in Visual Studio 2022 version 17.7, you can also autodecompile .NET code. For more information, see [Autodecompile code](../debugger/decompilation.md#autodecompile-code).
+     ::: moniker-end
+
 1. If the symbols don't load, select **Symbol Settings** to open the **Options** dialog, and specify or change symbol loading locations.
 
    You can download symbols from the public Microsoft Symbol Servers or other servers, or load symbols from a folder on your computer. For details, see [Configure location of symbol files and loading behavior](../debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md#configure-location-of-symbol-files-and-loading-options).

docs/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md

@@ -300,6 +300,7 @@ During debugging, the **Modules** window shows the code modules the debugger is
 |**Symbol Load Information**|Shows the location of a loaded symbol file, or the locations that were searched if the debugger cannot find the file.|
 |**Symbol Settings**|Opens the **Options** > **Debugging** > **Symbols** page, where you can edit and add symbol locations.|
 |**Always Load Automatically**|Adds the selected symbol file to the list of files that are automatically loaded by the debugger.|
+|**Decompile Source to Symbol File**|For .NET code, you can choose this option and then follow instructions in [Generate and embed sources for an assembly](../debugger/decompilation.md#generate-and-embed-sources-for-an-assembly).|
 
 ### Use the No Symbols Loaded/No Source Loaded pages
 

docs/debugger/toc.yml

@@ -366,26 +366,6 @@
     items:
     - name: 64-Bit applications
       href: debug-64-bit-applications.md
-    - name: UWP apps
-      items:
-      - name: Debug UWP apps >>
-        href: /windows/uwp/debug-test-perf/deploying-and-debugging-uwp-apps
-      - name: Debug UWP apps on a remote machine
-        href: run-windows-store-apps-on-a-remote-machine.md
-      - name: Run UWP apps in the simulator
-        href: run-windows-store-apps-in-the-simulator.md
-      - name: Deploy UWP apps from Visual Studio
-        href: deploy-windows-store-apps-from-visual-studio.md
-      - name: Debug an installed app package
-        href: debug-installed-app-package.md
-      - name: Inspect XAML properties while debugging >>
-        href: ../xaml-tools/inspect-xaml-properties-while-debugging.md
-      - name: Write and debug running XAML code >>
-        href: ../xaml-tools/xaml-hot-reload.md
-      - name: Debug XAML in Blend >>
-        href: ../xaml-tools/debug-xaml-in-blend.md
-      - name: How to trigger suspend, resume, and background events
-        href: how-to-trigger-suspend-resume-and-background-events-for-windows-store-apps-in-visual-studio.md
     - name: .NET
       items:
       - name: Recommended property settings
@@ -424,6 +404,26 @@
           href: how-to-debug-the-onstart-method.md
       - name: F#
         href: debugging-f-hash.md
+    - name: UWP apps
+      items:
+      - name: Debug UWP apps >>
+        href: /windows/uwp/debug-test-perf/deploying-and-debugging-uwp-apps
+      - name: Debug UWP apps on a remote machine
+        href: run-windows-store-apps-on-a-remote-machine.md
+      - name: Run UWP apps in the simulator
+        href: run-windows-store-apps-in-the-simulator.md
+      - name: Deploy UWP apps from Visual Studio
+        href: deploy-windows-store-apps-from-visual-studio.md
+      - name: Debug an installed app package
+        href: debug-installed-app-package.md
+      - name: Inspect XAML properties while debugging >>
+        href: ../xaml-tools/inspect-xaml-properties-while-debugging.md
+      - name: Write and debug running XAML code >>
+        href: ../xaml-tools/xaml-hot-reload.md
+      - name: Debug XAML in Blend >>
+        href: ../xaml-tools/debug-xaml-in-blend.md
+      - name: How to trigger suspend, resume, and background events
+        href: how-to-trigger-suspend-resume-and-background-events-for-windows-store-apps-in-visual-studio.md
     - name: C/C++ code
       items:
       - name: Debug native code