Open crispyricepc opened 4 years ago
This is an issue with the editor and the build task generated for debugging yielding back the same error. We could investigate if there is a not-too-complicated way to de-duplicate things, or just not have the build task also yield back errors.
This is an issue with the editor and the build task generated for debugging yielding back the same error. We could investigate if there is a not-too-complicated way to de-duplicate things, or just not have the build task also yield back errors.
Perhaps a quick suggestion on how it could be fixed. The problems panel could check to see whether identical error codes appear at the same coordinates and ensure to only show one of them?
It'll bear some investigation. One of the issues is that activities in the editor and activities that invoke build are completely orthogonal. In Visual Studio, this massively complicates things (i.e., diagnostics could be coming from different threads and processes), leading to some problems and sometimes "sticky" errors. We're not sure if those same kinds of problems are relevant here or not.
@CRISPYricePC For a workaround, in your .vscode/tasks.json, replace "problemMatcher": "$mscompile"
with "problemMatcher": []
.
This is not a VSCode or panel issue, messages are duplicated with a dotnet build on command line also, always.
Environment data
Steps to reproduce
Create a new dotnet core project using
dotnet new console
Select yes to generate tasks.json and launch.json defaults Remove the semicolon in the auto-generated Hello World code Run the build taskExpected behavior
Only one
CS1002
error saying "; expected"Actual behavior
Two
CS1002
errors pointing to the same line, one with an included full path, another without oneScreenshots