Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Most features are basically broken randomly on vscode 1.43
See original GitHub issueEnvironment data
dotnet --info output:
.NET Core SDK (reflecting any global.json):
Version: 3.1.201
Commit: b1768b4ae7
Runtime Environment:
OS Name: Windows
OS Version: 10.0.19041
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\3.1.201\
Host (useful for support):
Version: 3.1.3
Commit: 4a9f85e9f8
.NET Core SDKs installed:
3.1.201 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
.NET Core SDK (reflecting any global.json):
Version: 3.1.201
Commit: b1768b4ae7
Runtime Environment:
OS Name: debian
OS Version: 10
OS Platform: Linux
RID: debian.10-x64
Base Path: /usr/share/dotnet/sdk/3.1.201/
Host (useful for support):
Version: 3.1.3
Commit: 4a9f85e9f8
.NET Core SDKs installed:
3.1.201 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.1.3 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.3 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
VS Code version: 1.43.2
C# Extension version: 1.21.15
Steps to reproduce
Open and edit a fresh new dotnet new classlib project.
Expected behavior
Everything would work fine, and if there is a problem, there would be some warn or fail output in the OmniSharp Log
Actual behavior
Language support would never start until you make a change to the source file.
No warn or fail reported, and everything looks harmonious.
Auto-completion for adding namespace using disappears.
All compiler errors are not detected except for syntax lexer/parser errors.
Types from nuget packages are not respected.
Some type inference does not work.
Phantom break points when debugging.
Build & launch sometimes have different behavior from the output built from command line, which bring strange problems like .so file not found when running a asp.net core project on linux, some properties in .props are ignored, or some project does not output executable files.
Random collections of these problems appear by different, and are even not able to determine whether they appear randomly or consistently. The occurrence of these problems could vary from different OS and/or project types.
I tried on both on Windows and WSL2 Debian, both default or "latest" version.
There are always some of these problems that make VSCode current version not an usable C# editor any more.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m noticing on
1.43.2that omnisharp just isn’t doing anything, or appears to be having a very hard time in my projects.It’s hard to explain because the only symptoms I’m seeing are behavioural. It manifests in weird ways like intellisense not working at all, ctrl-clicking on anything results in the little progress bar running across the top of the screen, stopping and then nothing happening. I can’t refactor anything.
It just seems…dead?
Logs show nothing out of the ordinary (I think?)…
@cartermp I have the same issue on a modern VS Code and tye no longer installs because of a download error: