Code reports errors in removed source files

[jrieken]

From @jeffschwMSFT on February 19, 2016 18:13

On my OS X Yosemite machine running Code, I was adding/removing code in a solution. One of the files I removed had a C# build error. The interesting thing was the the error persisted in my Code session even after deleting the file (control - click - delete). The error only went away once I closed the folder and reopened.

Copied from original issue: microsoft/vscode#3174

[jrieken]

From @egamma on February 20, 2016 15:12

Not clear whether this is Omnisharp or the Code marker infrastructure. The fact that the error count drops to 0 indicates that the marker is properly removed when the file is deleted.

[jrieken]

From @dbaeumer on February 29, 2016 15:53

Since the error counts drops to zero I suspect this being a problem in OmniSharp land

[jrieken]

Omnisharp doesn't really support delete...

[jeffschwMSFT]

I wanted to put this higher on the stack. After using VS Code more I have found that this issue is even worse if you rename a file. VS Code will always give you the error that XYZ class has already been defind.

[duraz0rz]

I've recently come across this bug.

Steps to reproduce:

1. Introduce an error in your code. Remove a semi-colon or something.
2. Delete the file.

Expected: The error should go away.
Actual: The error stays in VSCode, even after editing other code. I did not observe the error count go down to 0; it remains at 1.

A workaround is to restart Omnisharp after changing the file system (add/rename/delete files from solution).

[DustinCampbell]

We're going to use #785 to track the file renaming issue. I believe the other issues mentioned here are addressed.