Merging changes synced from https://github.com/MicrosoftDocs/visualstudio-docs-pr (branch live)

Author: Learn Build Service GitHub App

docs/debugger/debugger-tips-and-tricks.md

@@ -97,17 +97,12 @@ It's easy to view variables using debugger windows like the **Watch** window. Ho
 
 1. Find the variable in the **Locals** window (**Debug > Windows > Locals**), right-click the variable, and select **Make Object ID**.
 
-    ::: moniker range="visualstudio"
-
-    ![Screenshot showing how to create an object ID in Visual Studio.](media/visualstudio/debug-tips-watch-create-object-id.png)
-
-    ::: moniker-end
-
-    ::: moniker range="vs-2022"
-
-    ![Screenshot showing how to create an object ID.](media/dbg-tips-watch-create-object-id.png "CreateObjectID")
-
-    ::: moniker-end
+   ::: moniker range="visualstudio"
+   ![Screenshot showing how to create an object ID in Visual Studio.](media/visualstudio/debug-tips-watch-create-object-id.png)
+   ::: moniker-end
+   ::: moniker range="vs-2022"
+   ![Screenshot showing how to create an object ID.](media/dbg-tips-watch-create-object-id.png "CreateObjectID")
+   ::: moniker-end
 
 1. You should see a **$** plus a number in the **Locals** window. This variable is the object ID.
 
@@ -160,29 +155,21 @@ In addition, you can enter functions in the **Immediate** window to view return
 When working with strings, it can be helpful to view the entire formatted string. To view a plain text, XML, HTML, or JSON string, click the magnifying glass icon ![VisualizerIcon](../debugger/media/dbg-tips-visualizer-icon.png "Visualizer icon") while hovering over a variable containing a string value.
 
 ::: moniker range="visualstudio"
-
-![Screenshot that shows how to open a String Visualizer in Visual Studio.](media/visualstudio/debug-tips-string-visualizers-2.png "OpenStringVisualizer")
-
+![Screenshot that shows how to open a String Visualizer.](../debugger/media/visualstudio/debug-tips-string-visualizers-2.png "OpenStringVisualizer")
 ::: moniker-end
 
 ::: moniker range="vs-2022"
-
-![Screenshot that shows how to open a String Visualizer.](media/dbg-tips-string-visualizers.png "OpenStringVisualizer")
-
+![Screenshot that shows how to open a String Visualizer.](../debugger/media/dbg-tips-string-visualizers.png "OpenStringVisualizer")
 ::: moniker-end
 
 A string visualizer may help you find out whether a string is malformed, depending on the string type. For example, a blank **Value** field indicates the string is not recognized by the visualizer type. For more information, see [String Visualizer Dialog Box](../debugger/string-visualizer-dialog-box.md).
 
 ::: moniker range="visualstudio"
-
-![Screenshot that shows the JSON String Visualizer in Visual Studio.](media/visualstudio/debug-tips-string-visualizer-json.png "JSONStringVisualizer")
-
+![Screenshot that shows the JSON String Visualizer.](../debugger/media/visualstudio/debug-tips-string-visualizer-json.png "JSONStringVisualizer")
 ::: moniker-end
 
 ::: moniker range="vs-2022"
-
-![Screenshot that shows the JSON String Visualizer.](media/dbg-tips-string-visualizer-json.png "JSONStringVisualizer")
-
+![Screenshot that shows the JSON String Visualizer.](../debugger/media/dbg-tips-string-visualizer-json.png "JSONStringVisualizer")
 ::: moniker-end
 
 For a few other types such as DataSet and DataTable objects that appear in the debugger windows, you can also open a built-in visualizer.
@@ -208,15 +195,11 @@ The debugger breaks into your code on unhandled exceptions. However, handled exc
 The **Exception Settings** dialog box allows you to tell the debugger to break into code on specific exceptions. In the illustration below, the debugger breaks into your code whenever a `System.NullReferenceException` occurs. For more information, see [Managing exceptions](../debugger/managing-exceptions-with-the-debugger.md).
 
 ::: moniker range="visualstudio"
-
-![Screenshot that shows the Exception Settings dialog box in Visual Studio.](media/visualstudio/debug-tips-exception-settings.png "ExceptionSettingsDialogBox")
-
+![Screenshot that shows the Exception Settings dialog box.](../debugger/media/visualstudio/debug-tips-exception-settings.png "ExceptionSettingsDialogBox")
 ::: moniker-end
 
 ::: moniker range="vs-2022"
-
-![Screenshot that shows the Exception Settings dialog box.](media/dbg-tips-exception-settings.png "ExceptionSettingsDialogBox")
-
+![Screenshot that shows the Exception Settings dialog box.](../debugger/media/dbg-tips-exception-settings.png "ExceptionSettingsDialogBox")
 ::: moniker-end
 
 ## Change the execution flow
@@ -253,15 +236,11 @@ To attach to your running app, the debugger loads symbol (.pdb) files generated
 Open the **Modules** window while debugging by selecting **Debug > Windows > Modules**. The **Modules** window can tell you what modules the debugger is treating as user code, or [*My Code*](../debugger/just-my-code.md), and the symbol loading status for the module. In most scenarios, the debugger automatically finds symbol files for user code, but if you want to step into (or debug) .NET code, system code, or third-party library code, extra steps are required to obtain the correct symbol files.
 
 ::: moniker range="visualstudio"
-
-![Screenshot that shows how to view symbol information in the Modules window in Visual Studio.](media/visualstudio/debug-tips-modules-window.png "ViewSymbolInformation")
-
+![Screenshot that shows how to view symbol information in the Modules window.](../debugger/media/visualstudio/debug-tips-modules-window.png "ViewSymbolInformation")
 ::: moniker-end
 
 ::: moniker range="vs-2022"
-
-![Screenshot that shows how to view symbol information in the Modules window.](media/dbg-tips-modules-window.png "ViewSymbolInformation")
-
+![Screenshot that shows how to view symbol information in the Modules window.](../debugger/media/dbg-tips-modules-window.png "ViewSymbolInformation")
 ::: moniker-end
 
 You can load symbol information directly from the **Modules** window by right-clicking and choosing **Load Symbols**.

docs/debugger/media/visualstudio/data-tips-examples.png

@@ -1,7 +1,7 @@
 ---
 title: "Remote debug ASP.NET on an IIS computer"
 description: Learn how to set up and configure a Visual Studio ASP.NET MVC 4.8 application, deploy it to IIS, and attach the remote debugger from Visual Studio. 
-ms.date: 04/23/2024
+ms.date: 05/28/2026
 ms.topic: how-to
 author: "mikejo5000"
 ms.author: "mikejo"
@@ -18,14 +18,15 @@ To debug an ASP.NET application that has been deployed to IIS, install and run t
 This guide explains how to set up and configure a Visual Studio ASP.NET MVC 4.8 application, deploy it to IIS, and attach the remote debugger from Visual Studio.
 
 > [!NOTE]
-> To remote debug ASP.NET Core instead, see [Remote Debug ASP.NET Core on an IIS Computer](../debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md). For Azure App Service, see [Remote debug ASP.NET Core on Azure](/training/modules/dotnet-debug-visual-studio-azure-web-apps/) or, for Visual Studio Enterprise, use the [Snapshot Debugger](../debugger/debug-live-azure-applications.md) (.NET 4.6.1 required).
+> To remote debug ASP.NET Core instead, see [Remote Debug ASP.NET Core on an IIS Computer](../debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md). For Azure App Service, see [Remote debug ASP.NET Core on Azure](../debugger/remote-debugging-azure-app-service.md).
 
 ## Prerequisites
 
 Visual Studio 2019 or a later version is required to follow the steps shown in this article.
 
 These procedures have been tested on these server configurations:
 
+* Windows Server 2025 and IIS 10
 * Windows Server 2022 and IIS 10
 * Windows Server 2012 R2 and IIS 8 (For Windows Server 2008 R2, the server steps are different)
 
@@ -123,15 +124,14 @@ After the app deploys successfully, it should start automatically. If the app do
 When you're ready, switch to a debug configuration.
 
 > [!IMPORTANT]
-> If you choose to debug a Release configuration, you disable debugging in the *web.config* file when you publish.
+> If you choose a Release configuration, you disable debugging in the *web.config* file when you publish.
 
 ::: moniker range=">=vs-2022"
 1. Select **More Options** > **Edit** to edit the profile, and then select **Settings**.
 1. Select a **Debug** configuration, and then select **Remove additional files at destination** under the **File Publish** options.
 1. Select **Save** and then republish the app.
 ::: moniker-end
 
-
 > [!WARNING]
 > Using username and password credentials (basic authentication) is not the most secure method of authentication. Whenever possible, use alternative methods. For example, consider publishing to a package from Visual Studio, and then use *WebDeploy.exe* from a command line to deploy the package. With that method, you can use IIS Manager to configure authorized Windows users who can publish to the web server, and run *WebDeploy.exe* under that Windows user account. See [Installing and Configuring Web Deploy on IIS 8.0 or Later](/iis/install/installing-publishing-technologies/installing-and-configuring-web-deploy-on-iis-80-or-later). If you do use password credentials, be sure to use a strong password, and secure the password from being leaked or shared.
 
@@ -263,7 +263,7 @@ Starting in Visual Studio 2022 version 17.10 Preview 2, the Attach to Process di
 - If you can't connect to the host using the host name, try the IP address instead.
 - Make sure the required ports are open on the remote server.
 - Verify that the version of ASP.NET used in your app is the same as the version you installed on the server. For your app, you can view and set the version in the **Properties** page. To set the app to a different version, that version must be installed.
-- If the app tried to open, but you see a certificate warning, choose to trust the site. If you already closed the warning, you can edit the publishing profile, a *.pubxml file, in your project and add the following element (for test only): `<AllowUntrustedCertificate>true</AllowUntrustedCertificate>`
+- If the app tried to open, but you see a certificate warning, choose to trust the site. If you already closed the warning, you can edit the publishing profile, a *.pubxml* file in the *Properties\PublishProfiles* folder, and add the following element (for test only): `<AllowUntrustedCertificate>true</AllowUntrustedCertificate>`
 - After it's deployed, start the app in IIS to test that it deployed correctly.
 - Check the Output window in Visual Studio for status information, and check your error messages.