-
Notifications
You must be signed in to change notification settings - Fork 676
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
PCL assembly shows erroneous errors when using Microsoft.NETCore.Portable.Compatibility #1221
Comments
#424 doesn't look related to me. That was about a very specific sort of project.json project that wraps around a library using "bin". Could you provide your OmniSharp Log for me after you open the project in VS Code? Just select |
Here you go!
|
Thanks! I can repro and am debugging. It appears to me like the problem is due to mscorlib 4.0.0.0 (from Microsoft.NETCore.Portable.Compatibility) isn't unifying with mscorlib 2.0.5.0, which NodaTime references. |
Hmmm... If I migrate the project from project.json to .csproj, it appears that it works properly. |
OK. I've got a fix. As suspect, it was not related to #424. |
@tetious: I just wanted to let you know that we've released the first beta for 1.8, which contains the fix for this issue: https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.8.0-beta1. You can use these instructions to install a beta release. |
Thanks very much for the super-quick fix! I can confirm that the beta is working properly here. |
Awesome! Thanks for confirming. |
This is a followup to issue #424, which I think may be related.
Environment data
dotnet --info
output:VS Code version: 1.9.1
C# Extension version: 1.7.0
Steps to reproduce
See sample project here:
https://github.com/tetious/NodaTimePCLTest
This will possibly work with other PCL libraries, but it is super easy to repro with NodaTime.
Expected behavior
No errors.
Actual behavior
Use nearly any part of NodaTime and you'll get red squigglies.
Build/run works fine.
Let me know if I can give you any more info, and thanks!
The text was updated successfully, but these errors were encountered: