Omnisharp does not display all errors/warnings in VSCode

[HalfVoxel]

Environment data

dotnet --info output:
.NET Command Line Tools (1.0.0-preview2-003131)

Product Information:
Version: 1.0.0-preview2-003131
Commit SHA-1 hash: 635cf40e58

Runtime Environment:
OS Name: Mac OS X
OS Version: 10.11
OS Platform: Darwin
RID: osx.10.11-x64

VS Code version:
1.6.0

C# Extension version:
1.4.1

Steps to reproduce

Open a project with several errors/warnings in it (a project that you can replicate this bug in is available upon request).

Expected behavior

Omnisharp displays all errors/warnings in the Problems window in VSCode

Actual behavior

Omnisharp only displays a few or no messages even though in the omnisharp log I can clearly see them and have verified that they are valid errors/warnings (or... at least sometimes the log contains all warnings/errors, sometimes it does not). I have uploaded my omnisharp log here.
This is in a clean install with no other extensions. The project is a Unity project, but I doubt that should matter.

VSCode also logs "Some projects have trouble loading. Please review the output for more details." however I cannot see anything suspicious in the log even with verbose logging enabled. Though it is pretty large so I might have missed something.

Restarting VSCode or the Omnisharp server does not solve it.

I have not tried to reduce my project to a smaller size and checked if it still happens, but I am more than happy to share my project with anyone to try to debug it.

For a while it would simply display one or sometimes a few warnings (I was fixing a lot of unused 'using' declarations) and I had to fix the single warning that was displayed, wait while it re-processed everything and then fix the next warning that would then show up.

[DustinCampbell]

Hi, if this is a largeish Unity project (e.g. >= 1000 .cs source files), this is generally expected. In that case, the extension will only retrieve errors and warnings for open files to avoid constantly chewing CPU.

FYI, the link to your omnisharp log does not work me.

[HalfVoxel]

Hi

It is large, but nowhere near that large.

$ ls **/*.cs | wc
273

[HalfVoxel]

In any case, the files were open.
Huh, that's odd, it works just fine for me.

[DustinCampbell]

I'd love to take a look at your project if you're able to provide it. Perhaps we broke something. Also, you might consider trying the latest beta of the C# extension available here and see if that improves the issue.

[HalfVoxel]

Here are some screenshots and the log that is visible in them

http://pastebin.com/Us51C8Us

[HalfVoxel]

Also, you might consider trying the latest beta of the C# extension available here and see if that improves the issue.

Ok, is it possible to install that from within VSCode or do I have to do some manual work here? (this is literally the first time I have tried using VSCode, so I am not very familiar with how the plugins work yet).

I will send you an email.

[DustinCampbell]

FWIW, the warnings in the log are produced when OmniSharp uses MSBuild to perform a design-time compilation of your project in order to gather up source files and references. However, OmniSharp does not return those. There's a separate endpoint that requires errors and warnings live from your code.

[DustinCampbell]

Ok, is it possible to install that from within VSCode or do I have to do some manual work here? (this is literally the first time I have tried using VSCode, so I am not very familiar with how the plugins work yet).

You can install it within VS Code. Go to the Extensions pane, click the three dots at the top-right of the pane and select "Install from VSIX..."

[HalfVoxel]

FWIW, the warnings in the log are produced when OmniSharp uses MSBuild to perform a design-time compilation of your project in order to gather up source files and references. However, OmniSharp does not return those. There's a separate endpoint that requires errors and warnings live from your code.

Ok, but it is supposed to be able to get those warnings/errors from the other endpoint as well, right?

[HalfVoxel]

You can install it within VS Code. Go to the Extensions pane, click the three dots at the top-right of the pane and select "Install from VSIX..."

Installing the beta did not seem to resolve the problem unfortunately. Here is the log for the beta version: http://pastebin.com/r7gh70Bd

I sent you an email with the project.

[bsell93]

I think I am experiencing something similar. I attempted to install the previously mentioned beta version with no change. For me the errors show up for a second after saving and then disappear. I have a short video of it (please forgive the watermark). I found that this bug came about after updating to the just released version of VSCode (v1.6)

[HalfVoxel]

@bsell93 I also saw that once. The errors were not valid however, I think it was because I had just deleted some files and Unity had not rewritten the project file, so omnisharp was logging errors about that. I don't think it is related to this issue however.

[bsell93]

I see. Yeah, I am not sure what is going on. They are definitely errors, because I intentionally made them 😁.

[shlapkoff]

I have the same problem. This happened after the update VS Code to version 1.6

[shlapkoff]

I found a solution: in v.1.5.3 all working.

https://code.visualstudio.com/updates/v1_5