Window > Reset Window Layout
Answer from Sam Harwell on Stack OverflowThe error list of the current Visual Studio document keeps disappearing
VS Error List doesn't show errors from build failure
VS 2022 won't show build failure errors in the Error List from razor files that aren't currently open
Visual Studio: Can I make the Error List always appear when build/run fails?
Hi @tovia schlesinger ,
Welcome to Microsoft Q&A!
Which version of Visual Studio are you using?
Please check the option “Always show error list if build finishes with errors” under Tools > Options > Projects and Solutions > General.
Then, delete the hidden .vs folder in the project folder and re-launch your Visual Studio to try again.
You can select the “Build + IntelliSense” in the error list to show all errors.
Sincerely,
Anna
*
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.
how to add Spire.PDf and Spire.xls
Does anyone know of a way to fix this? This problem has been since VS first supported razor view files years ago and still hasn't been addressed. If there is a razor build error, but the razor file with the error is not open, the Error List will not show the error.
However if you turn on diagnostic-level Build Output Verbosity in the Options, the Build Output window will show the razor filename and error message.
So why can't VS add that error to the Eror List if it is appearing in the build logs that VS is supposed to be parsing?
Right hand side of ErrorList, select Build + Intellisense. Worked for me
I'm seeing this in 2015 every once and a while. For me changing the "Show issues generated" drop down gets them to show up. Even if I was already on "Build + IntelliSense", dropping it down to "Build Only" or "IntelliSense Only" can get them to display (without having to rebuild). Sometimes I can take it back to B+I and keep the revealed errors, sometimes not. Rather weird.
This had been working for a while, and now suddenly started with the same behavior as before. Builds are failing, but nothing errors are shown in the error list if it's set to "Build + IntelliSense". If I switch to "Build Only" I can see the errors, but only after a build. It won't show any syntax errors just from loading the project. This started happening again a few days ago. I am fully up to date using VS 2022 17.11.2.
I came here looking for a solution to the same thing. I have found if I change the view to Build only I can see the errors. If I have the view as Build + Intellisense then the errors do not show.
This has only recently started happening so possibly with a recent update?
Deleting the .suo file might help when encountering erratic Visual Studio behavior.
The file contains user defined solution settings, including breakpoints, debug options, bookmarks and may get corrupted or saved in an undesired state.
If you delete it, a new .suo file will be created once you reopen the solution in Visual Studio.
You need to turn on the underline errors in the editor options in Visual Studio.
These options can be found here:
Tools > Options > Text Editor > C# > Advanced > Editor Help