Skip to content
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

Errors/Warnings failing again #889

Closed
Novack opened this issue Nov 8, 2016 · 10 comments
Closed

Errors/Warnings failing again #889

Novack opened this issue Nov 8, 2016 · 10 comments

Comments

@Novack
Copy link

Novack commented Nov 8, 2016

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
Copy link

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

@Novack
Copy link
Author

Novack commented Nov 15, 2016

@HawkenKing please use the 👍 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
Copy link
Member

DustinCampbell commented Nov 16, 2016

@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 microsoft/vscode#15585 to track getting this fixed in VS Code.

@DustinCampbell
Copy link
Member

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
Copy link
Author

Novack commented Nov 17, 2016

Thank you.

@Novack
Copy link
Author

Novack commented Nov 23, 2016

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

@DustinCampbell
Copy link
Member

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
Copy link
Author

Novack commented Nov 23, 2016

@DustinCampbell Sorry man. Got carried by the anxiety.

@DustinCampbell
Copy link
Member

No problem. 😄

@jrieken
Copy link
Contributor

jrieken commented Nov 24, 2016

re #889 (comment) correct. This is in insiders already today and will be in 1.8 which arrives mid december

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants