OmniSharp doesn't load on my systems if the root folder has a C# submodule
See original GitHub issueIssue Description
If I have a project with a Git submodule, OmniSharp doesn’t work - it doesn’t even seem to load (OmniSharp Log window is empty)
I can reproduce this reliably on two machines that are similar (one is a Manjaro VM and one is Manjaro dual-boot)
Steps to Reproduce
git clone https://github.com/deengames-prototypes/haven-island
git submodule update --init
- Open VSCode to the root of
haven-island
Expected Behavior
OmniSharp should run as normal.
Actual Behavior
OmniSharp doesn’t even load; no autocorrect, etc.
Logs
OmniSharp log
C# log
Environment information
VSCode version: 1.42.1 C# Extension: 1.21.12
Mono Information
OmniSharp using global mono :6.4.0Dotnet Information
.NET Core SDK (reflecting any global.json): Version: 3.1.100 Commit: cd82f021f4Runtime Environment:
OS Name: manjaro
OS Version:
OS Platform: Linux
RID: arch-x64
Base Path: /usr/share/dotnet/sdk/3.1.100/
Host (useful for support): Version: 3.1.1 Commit: a1388f194c
.NET Core SDKs installed: 3.1.100 [/usr/share/dotnet/sdk]
.NET Core runtimes installed: Microsoft.AspNetCore.App 3.1.1 [/usr/share/dotnet/shared/Microsoft.AspNetCore.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
Extension | Author | Version |
---|---|---|
csharp | ms-vscode | 1.21.12 |
Csharp-ASPNETCore | rahulsahay | 1.11.0 |
godot-tools | geequlim | 1.0.3 |
mono-debug | ms-vscode | 0.15.8 |
powershell | ms-vscode | 2020.1.0 |
python | ms-python | 2020.2.64397 |
vscode-nxunit-test-adapter | wghats | 0.1.3 |
vscode-test-explorer | hbenl | 2.17.0 |
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (5 by maintainers)
Top GitHub Comments
@nightblade9 Can you please share the OmniSharp log from the Output pane? I followed your steps and was able to load
I found a work-around in this issue:
F1
>OmniSharp: Select Project
>HavenIsland.sln
and everything loads/runs as expected.@JoeRobich when you get a minute, can you please try something to verify my hypothesis: from the cloned root, run
git submodule update --init
and then close and re-open VSCode to see if the problem reproduces.I am 100% sure this worked before (for weeks) - I don’t know why it’s suddenly breaking on a multi-solution project. But that same GitHub issue (or another one) indicates that VSCode doesn’t work with multi-root solutions (I have two
.sln
files in this workspace).