-
Notifications
You must be signed in to change notification settings - Fork 420
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
Script project system fails to initialize in VS Code 1.15.0 (1.30.0 release of OmniSharp) on macOS #1184
Comments
It really looks like a corrupt release.
|
Seeing the same behaviour on MacOS and Ubuntu. Windows seems fine |
OK I have spent some more time analyzing the problem and while I have not fully understood what happened, the degree of udnerstanding has led me to producing a fix which is in PR #1185 What I wrote before is indeed true (and it affects not just macOS but also Linux)
Now, when building from the source, on macOS:
The difference in this case is rather subtle and my understanding breaks down so it would have to be @DustinCampbell or @david-driscoll that could explain this better, what is really the difference here? This only happens when building on macOS. On Windows, the executable in both cases works fine. Now, when I update my VS Code on Mac to Onto the core issue now. SO to fix it once and for all, I have updated the code to pick up these Roslyn pieces from the current process (from current The PR was tested on both Linux and macOS and the problem has been fixed. |
@filipw, I have no idea why Cake's publish would be different. However, I'm definitely in favor of fewer dependency's on the It seems to me that we should add a scripting test in C# for VS Code. Such a test would have failed on omnisharp-vscode's Travis runs. Do you want to take a stab at that? cc @rchande for help with this. |
that's a very good idea - I will definitely have a look at that 👍 |
@filipw Let me know if you need any help adding the test! |
Yes, let's definitely get a test added. Even something that just opens a csx file and verifies that signature help appears or something like that. |
@filipw: We have a new beta of C# for VS Code that includes your fix: https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.15.2-beta1. Would you mind validating it to ensure the scripting issue is fixed? |
thanks a lot, works perfectly 🔥 |
Environment data
dotnet --info
output:2.1.300-rc1-008673
VS Code version: 1.23.1
C# Extension version: 1.15.0
Steps to reproduce
temp
folder with adummy.csx
and the following contentExpected behavior
Script project system initializes correctly and language services light up.
Actual behavior
Script project system fails to initialize. This doesn't crash OmniSharp but prevents language services for CSX.
The output is
Updating VS Code to use OmniSharp
latest
(1.30.1-beta.15) or building frommaster
branch fixes the problem.The problem doesn't happen on Windows.
@DustinCampbell @rchande I am not sure if this isn't some packaging problem in VS Code because I'd swear that release worked fine on macOS.
anyway, would it be possible to take the latest OmniSharp HEAD, with Roslyn 2.8.0 and release as 1.15.1 extension?
The text was updated successfully, but these errors were encountered: