Visual Studio: Can I make the Error List always appear when build/run fails?

MicrosoftAdmin 1 Reputation point
2021-05-22T06:42:45.253+00:00

The Error List is docked at the bottom of the window, and I often hide the Error List whilst coding, because the vertical space is limited (damn wide monitors).

If I remember it correctly, I think the Error List used to appear automatically whenever build/run fails with an error. But with the recent versions of VS, it seems that it only automatically appears for the first build/run failure after successful build/run (or no previous build/run at all). That is in the following scenario, it does not automatically appear.

  1. I press Build, and it succeeds.
  2. I edit the code and make 3 errors.
  3. I press Build, and the Error List automatically shows up.
  4. I hide the Error List.
  5. I fix 2 of the 3 errors.
  6. I press Build.

In the scenario above, of course, the code does not run because it has 1 remaining error, and the Error List does not show up. I have to click the Error List manually. Is this an intended behaviour or a bug?

Developer technologies | Visual Studio | Other
{count} votes

1 answer

Sort by: Most helpful
  1. Tianyu Sun-MSFT 34,436 Reputation points Microsoft External Staff
    2021-05-24T05:43:06.203+00:00

    Hi @MicrosoftAdmin ,

    Thank you for sharing the screen recording with us.

    I tested by using latest version of VS 2019(v16.9.6), but I also failed reproduce your issue, the Output window and Error List window showed up normally.

    Please try following steps and if they don’t work, please directly report this issue to Visual Studio Product Team on Developer Community which @David Lowndes has suggested above.

    1). I suppose you have tried with a new project, if you haven’t tried, please try to create a new simple project and test again.

    2). Please try to repair VS from VS Installer.

    3). If you didn’t set many configurations for VS, you can try to reset VS settings(choose General on step 4).

    4). Please try to close all VS instances and delete the .vs, bin and obj folders, then restart VS and test again.

    Best Regards,
    Tianyu

    • If the answer is helpful, please click "Accept Answer" and upvote it.
      Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.