Merge pull request #14671 from MicrosoftDocs/main

Auto Publish – main to live - 2025-11-21 17:00 UTC

Author: learn-build-service-prod[bot]

docs/debugger/includes/prerequisites-dotnet-linux-ssh.md

@@ -20,4 +20,6 @@
 
 - On the Linux server, [install the .NET runtime on Linux](/dotnet/core/install/linux), and find the page matching your Linux distribution (such as Ubuntu). The .NET SDK is not required.
 
+  To make sure required .NET debugging services are available for debugging, avoid publishing the application as a single-file executable.
+
 - For comprehensive ASP.NET Core instructions, see [Host ASP.NET Core on Linux with Nginx](/aspnet/core/host-and-deploy/linux-nginx) and [Host ASP.NET Core on Linux with Apache](/aspnet/core/host-and-deploy/linux-apache).

docs/ide/how-to-report-a-problem-with-visual-studio.md

@@ -1,7 +1,7 @@
 ---
 title: Report a problem with Visual Studio
 description: Report a problem in Visual Studio by using the product installer or the built-in Feedback Tool, which allows you to easily add diagnostic information.
-ms.date: 3/14/2024
+ms.date: 11/17/2025
 ms.topic: how-to
 author: jasonchlus
 ms.author: jasonchlus
@@ -14,44 +14,49 @@ You can report a problem from either Visual Studio or its installer. The built-i
 
 Here are the steps to report a problem.
 
-1. **In Visual Studio**, select the feedback icon in the upper-right corner and select Report a Problem. You can also access the feedback tool  from the menu **Help** > **Send Feedback** > **Report a Problem**.
-    ![Screenshot showing the feedback icon selected in the upper right corner of the Visual Studio window and Report a Problem selected on the context menu.](media/feedback-button.png)
+1. **In Visual Studio**, select the feedback icon in the upper-right corner and select Report a Problem. You can also access the feedback tool from the menu: **Help** > **Send Feedback** > **Report a Problem**.
 
-    Alternatively, if you can't install Visual Studio or are unable to access the feedback tool within Visual Studio you can report a problem in the **Visual Studio Installer**.  If you have Visual Studio open, go to **Tools > Get Tools > Features...** to launch the installer, or launch it from the Start menu. In the installer, select the feedback icon in the upper-right corner and select **Report a Problem**.
+    ![Screenshot showing the feedback icon selected in the upper right corner of the Visual Studio window and Report a Problem selected on the context menu.](media/visualstudio/feedback-button.png)
+
+    Alternatively, if you can't install Visual Studio or are unable to access the feedback tool within Visual Studio you can report a problem in the **Visual Studio Installer**. If you have Visual Studio open, go to **Tools > Get Tools > Features...** to launch the installer, or launch it from the Start menu. In the installer, select the feedback icon in the upper-right corner and select **Report a problem**.
 
     ![Screenshot showing the feedback icon selected in the upper right corner of the Visual Studio Installer and Report a Problem selected on the context menu.](./media/report-a-problem-selected.png)
 
 1. Selecting **Report a Problem** will open [Developer Community](https://developercommunity.microsoft.com/VisualStudio) in your default browser and sign you in using the same account you're signed in to Visual Studio with.
 
    Note: If you are using an ad-blocker you may experience issues during sign-in. Disable the ad-blocker and try to sign in again.
 
-   ![Sign in to report a problem](../ide/media/feedback-browser-top.png)
+   ![Screenshot that shows how to sign in to report a problem.](../ide/media/visualstudio/feedback-browser-top.png)
 
 1. Start by entering the descriptive title of your bug report. It must be at least 25 characters long.
 
-    ![Report a problem](../ide/media/feedback-report.png)
+    ![Screenshot that shows how to report a problem.](../ide/media/visualstudio/feedback-report.png)
+
+1. Select a category for the problem.
 
-1. Once you start typing, possible duplicates are shown under the title field
+1. Start entering a description of the problem.
 
-    ![Search for duplicates](../ide/media/feedback-search.png)
+1. After you enter enough information, the **Search** button at the bottom of the page is enabled. Select this button to see a list of similar problems and solutions. 
 
-1. Select the possible duplicate bug reports to see if there is one matching your own problem. If there is, vote for it instead of creating your own ticket.
+    ![Screenshot that shows the Search button.](../ide/media/visualstudio/search-button.png)
 
-    ![Vote for duplicates](../ide/media/feedback-duplicate.png)
+1. Select the possible bug reports to see if there is one matching your own problem. If there is, vote for it instead of creating your own ticket.
 
-1. If no duplicates were found, continue by entering a description of the problem. It's important to be as clear as possible to increase the chances of us being able to reproduce the bug. Make sure to include clear reproduction steps.
+    ![Screenshot that shows the voting buttons.](../ide/media/visualstudio/feedback-duplicate.png)
 
-1. If relevant to the bug report, take a screenshot by checking the *Include Visual Studio screenshot* checkbox.  You can even crop the screenshot directly in the browser to remove any sensitive or unrelated parts.
+1. If no duplicates were found, continue by selecting **Can't find the solution**. When you select this button, you see the **Submit a ticket** tab. The information that you've already entered is still in the form. Complete the description if you haven't already done so. It's important to be as clear as possible to increase the chances of the engineering team being able to reproduce the bug. Make sure to include clear reproduction steps.
 
-    ![Take a screenshot](../ide/media/feedback-screenshot.png)
+1. If relevant to the bug report, take a screenshot by selecting the **Include Visual Studio screenshot**. You can even crop the screenshot directly in the browser to remove any sensitive or unrelated parts.
+
+    ![Screenshot that shows how to include a screenshot in a ticket.](../ide/media/visualstudio/feedback-screenshot.png)
     *Only Microsoft engineers can see the screenshot*
 
 1. <a name="trace"></a> Record your actions to reproduce the issue.
 
    One of the best ways to help the Visual Studio engineering team solve the problem is to provide a trace and heap dump files for them to look through. You can do that by recording the steps that resulted in the bug. A screenshot will be captured every time the mouse is clicked, but keyboard entry will not record screenshots.
-   1. Click **Start recording**. Wait a moment for the permissions prompt.
+   1. Select **Start recording**. Wait a moment for the permissions prompt.
    2. Go through your steps to record the issue. 
-   3. When finished, find the small pop-up window and click **Stop recording**. 
+   3. When finished, find the small pop-up window and select **Stop sharing**. 
 
    ![Record your actions](../ide/media/feedback-recording.png)
    *Only Microsoft engineers can see the recording*
@@ -61,11 +66,13 @@ Here are the steps to report a problem.
 
 1. Review the attached files and upload additional files if you believe it would help diagnose the issue.
 
-    ![Attached files](../ide/media/feedback-attachments.png)
+    ![Screenshot that shows the attached files.](../ide/media/visualstudio/feedback-attachments.png)
     *Only Microsoft engineers can see the attached files*
 
 1. The last step is to hit the **Submit** button. Submitting the report will send it directly into the internal Visual Studio bug reporting system awaiting triage.
 
+You will receive email updates about your ticket. After submitting the ticket, you can go to the [Home page](https://developercommunity.visualstudio.com/home) of the Developer Community site to view your feedback.
+
 Each one of your problem reports becomes a work item in our core engineering system, empowering you to engage directly with our product teams to help us identify and resolve impactful issues. Your feedback submitted with rich diagnostic information is critical to improving the Visual Studio product family. We really appreciate you taking the time to report problems.
 
 In addition, you can vote on feedback from other community members to bring more attention to a problem and help fix it faster.

docs/ide/media/visualstudio/feedback-attachments.png

@@ -1,7 +1,7 @@
 ---
 title: Collect ETL trace with PerfView, create minidumps
 description: Use the PerfView tool to create an ETL (event trace log) based on Event Tracing for Windows for troubleshooting issues with Visual Studio.
-ms.date: 07/18/2022
+ms.date: 11/17/2025
 ms.topic: how-to
 helpviewer_keywords:
   - "perfview"
@@ -32,13 +32,20 @@ Download PerfView from [GitHub](https://github.com/Microsoft/perfview/blob/main/
 ### Run PerfView
 
 1. Right-click on **PerfView.exe** in Windows Explorer and choose **Run as administrator** as admin.
+
 1. On the Collect menu, choose **Collect**.
+
 1. Check **Zip**, **Merge**, and **ThreadTime**.
+
 1. Open the Advanced Options menu and add the value `25c93eda-40a3-596d-950d-998ab963f367` in the Additional Providers text field.
+
 1. Increase **Circular MB** to 1000.
-1. Change **Current Dir** to save ETL traces to a specified folder and Data File if you are going to collect more than once.
+
+1. Change **Current Dir** to save ETL traces to a specified folder and Data File if you're going to collect more than once.
+
 1. To start recording data, choose the **Start Collection** button.
-1. To stop recording data, choose the **Stop Collection** button. The PrefView.etl.zip file will be saved in the specified directory.
+
+1. To stop recording data, choose the **Stop Collection** button. The PrefView.etl.zip file is saved in the specified directory.
 
 PerfView can store only the most recent data that fits into its buffer. Therefore, try to stop the collection as soon as possible after Visual Studio starts to freeze or slow down. Don't collect for more than 30 seconds after you hit a problem.
 
@@ -49,25 +56,47 @@ In some cases, Microsoft might ask for a minidump of a running Visual Studio pro
 ### Create the minidump file
 
 1. Start a new instance of Visual Studio.
+
 1. From the main menu, choose **Debug** > **Attach To Process**.
+
 1. Choose **Select**, and then select the relevant **Managed** and **Native** check boxes and choose **OK**.
 
    ::: moniker range=">= vs-2022"
+
    :::image type="content" source="../ide/media/vs-2022/attach-to-process.png" alt-text="Screenshot showing the codes types selected in the Attach To Process dialog.":::
+
    ::: moniker-end
    ::: moniker range="vs-2019"
+
    ![Screenshot showing the codes types selected in the Attach To Process dialog.](../ide/media/attach-to-process.png)
+
    ::: moniker-end
 
 1. Select the other Visual Studio instance to attach to from the list of running processes, and then choose **Attach**.
+
 1. From the main menu, choose **Debug** > **Break All**.
+
 1. From the main menu, choose **Debug** > **Save Dump As**.
 
 ### Get the call stacks from the minidump
 
 1. Open the dump file in Visual Studio.
-1. Go to **Tools** > **Options** > **Debugging** > **Symbols** and make sure that **Microsoft Symbol Servers** is checked in the **Symbol file (.pdb) locations**.
-1. Open the **Command** window (**View** > **Other Windows** > **Command Window**).
-1. Type ‘~*k’. The window displays all threads' call stacks.
-1. Copy all text from Command Window and save to a text file.
-1. Attach the txt file to the bug.
+
+:::moniker range="visualstudio"
+
+2. Open the **Tools** > **Options** pane and expand the **All Settings** > **Debugging** > **Symbols** > **Search Locations** section. Under **Symbol file (.pdb) locations**, confirm the **Microsoft Symbol Servers** checkbox is selected.
+
+:::moniker-end
+:::moniker range="<=vs-2022"
+
+2. Open the **Tools** > **Options** dialog and expand the **Debugging** > **Symbols** section. Under **Symbol file (.pdb) search locations**, confirm the **Microsoft Symbol Servers** checkbox is selected.
+
+:::moniker-end
+
+3. Open the **Command** window (**View** > **Other Windows** > **Command Window**).
+
+4. Type ‘~*k’. The window displays all threads' call stacks.
+
+5. Copy all text from Command Window and save to a text file.
+
+6. Attach the txt file to the bug.