-
Notifications
You must be signed in to change notification settings - Fork 25
[BUG] C# build errors are not highlighted #2046
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
After reproducing this issue a few times in new projects, I returned to my original project. The situation somewhat resolved: By selecting a file known to have an error, errors were shown. If a file with known errors was not opened, it would not show as having errors in the Explorer. This issue appears to be coincide with a syntax highlighting issue that I was also writing a bug on, meaning that classes, methods, and variables were given the same color treatment. I'm not satisfied with the fact that it "resolved itself" though. Something is broken. |
@tedbrownxr |
Thanks, I'll keep an eye out. Naturally, everything is behaving right now. Your comment explains another interesting symptom: when I open a project, such as a new project:
Before your comment, I could never quite understand what was triggering the "reset" of syntax highlighting. Now I can tell it's clearly something to do with the Project's loading status. This issue is highly reproducible: you just have to fully exit Visual Studio between sessions, and call |
@webreidi, the 'needs-more-info' label has been removed upon receiving further response from the original bug filer. |
Describe the Issue
In a C# Console project with known build errors (e.g. multiple errors shown when running "dotnet build"), no errors are shown in VS Code. You can even write random letters anywhere in the file: nothing shows up as a problem.
A reset of the project (removing sln, .vscode and re-opening) did not resolve the issue.
An update of the application and all related extensions did not resolve the issue.
This issue can be reproduced by creating a new project with:
Using:
Steps To Reproduce
No response
Expected Behavior
No response
Environment Information
No response
The text was updated successfully, but these errors were encountered: