Omnisharp-vscode: Errors/Warnings failing again

[Novack]

Environment data

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

Product Information:
Version: 1.0.0-preview2-003133
Commit SHA-1 hash: 74df06500c

Runtime Environment:
OS Name: Windows
OS Version: 6.1.7601
OS Platform: Windows
RID: win7-x64

VS Code version: 1.7.1

C# Extension version: 1.5.0beta4

Steps to reproduce

Install VSCode 1.7.1

Expected behavior

See issue #812 for details.

Actual behavior

After installing 1.7.1 the issue described in #812 is back again. Tried uninstalling and reinstalling 1.5.0beta4 without result.

As a side note, context and background, at the moment, Im forced to use VSPro.

[HawkenKing]

same here, when I move the cursor, the red underline squiggles disappear.

[Novack]

@HawkenKing please use the :+1: on the main post here, issues gets sorted using that criteria... ¬¬

Not that this is a small thingie, basically VS Code becomes obsolete for Unity developers. Im coming back to Visual Studio and ScriptInspector3. Is a pitty because I really like Code, but the C# support is unstable to say the least, debugging is clumsy and intellisense far too limited. I'll try again in a few years :)

(Not to mention that I took the time to post a few issues, some severely affecting functionality and got vastly ignored).

[DustinCampbell]

@HawkenKing, @Novack- it looks like this is actually a bug in VS Code. I investigated #883 and found that the issue is not caused by the C# extension. It's likely an easy fix though. The details are in #883. I've filed https://github.com/Microsoft/vscode/issues/15585 to track getting this fixed in VS Code.

[DustinCampbell]

It looks like a solid fix has been checked into VS Code. We should start seeing this working properly in VS Code Insiders builds soon.

[Novack]

Thank you.

[Novack]

@DustinCampbell happening again on latest stable setup: Code 1.7.2, omnisharp 1.5.3

[DustinCampbell]

I don't believe the fix is in VS Code 1.7.2, which is a recovery build with a very specific fix. It should be in VS Code Insider builds. cc @jrieken to confirm.

[Novack]

@DustinCampbell Sorry man. Got carried by the anxiety.

[DustinCampbell]

No problem. :smile:

[jrieken]

re https://github.com/OmniSharp/omnisharp-vscode/issues/889#issuecomment-262628438 correct. This is in insiders already today and will be in 1.8 which arrives mid december