-
Notifications
You must be signed in to change notification settings - Fork 677
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
Why can't omnisharp/vscode load this sln file? #3580
Comments
@ahmelsayed Sorry you are having troubles. I followed your instructions, also added a |
I did dotnet restore, and disabled all extensions but the WSL extension and C#. I still see the
Environment informationVSCode version: 1.42.1 Mono InformationOmniSharp using global mono :6.8.0Dotnet Information.NET Core SDK (reflecting any global.json): Version: 3.1.101 Commit: b377529961Runtime Environment: Host (useful for support): .NET Core SDKs installed: .NET Core runtimes installed: To install additional .NET Core runtimes or SDKs: Visual Studio Code Extensions
|
@ahmelsayed I found this related issue in the VSCode repo - microsoft/vscode#35798 The error is not ours and from the brief look at the OmniSharp log in your gif, it seems that things are loading properly. |
The WSL situation makes it look like this open VS Code issue - microsoft/vscode#75932 |
Sorry for not getting back to you earlier. The project loads fine when using vscode on Windows, only when accessing it from WSL like in the gif. I'll keep an eye on the issue, though I still don't really understand why it accepts the sln file if it's renamed, but not with its original name. |
I think I'm getting the same error in version 1.22.0. When trying to select a project or solution in a Remote WSL accessing a WSL 2 distro I get:
|
@victoralvesp Sorry you are running into this, but thank you for reporting. I'll reopen and take a look at what we might have missed. |
I found a workaround: if you rename the project/solution so it is the first in |
Hi... getting the same issue on 1.22.0 with Remote-WSL as @victoralvesp |
Issue Description
Trying to use vscode (with WSL remote development extention) with this project https://github.com/Azure/azure-functions-host doesn't work
Steps to Reproduce
Expected Behavior
To be able to select between
WebJobs.Script.Tests.E2E.sln
andWebJobs.Script.sln
Actual Behavior
Only
WebJobs.Script.Tests.E2E.sln
works. Changing toWebJobs.Script.sln
throws this errorand nothing happens.
Deleting
WebJobs.Script.Tests.E2E.sln
and restarting vscode, causes it to not even recognize the project as C#. Copying all the content fromWebJobs.Script.sln
toWebJobs.Script.Tests.E2E.sln
makes it work fine.Logs
I don't see any logs that seem to relate to the issue other than the screen size error mentioned above
I see this in
Log (Window)
outputOmniSharp log
C# log
Environment information
VSCode version: 1.42.1
C# Extension: 1.21.11
Mono Information
OmniSharp using global mono :6.8.0Dotnet Information
.NET Core SDK (reflecting any global.json): Version: 3.1.101 Commit: b377529961Runtime Environment:
OS Name: ubuntu
OS Version: 18.04
OS Platform: Linux
RID: ubuntu.18.04-x64
Base Path: /usr/share/dotnet/sdk/3.1.101/
Host (useful for support):
Version: 3.1.1
Commit: a1388f194c
.NET Core SDKs installed:
2.2.402 [/usr/share/dotnet/sdk]
3.0.102 [/usr/share/dotnet/sdk]
3.1.101 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.2.8 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.2.8 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.2 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.1 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.2.8 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.2 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.1 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
Visual Studio Code Extensions
The text was updated successfully, but these errors were encountered: