Omnisharp-vscode: The .NET Core Debugger is still being downloaded. See the C# Output Window for more information.

[tomitrescak]

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.3)

Product Information:
Version: 1.0.3
Commit SHA-1 hash: 37224c9917

Runtime Environment:
OS Name: Mac OS X
OS Version: 10.12
OS Platform: Darwin
RID: osx.10.12-x64
Base Path: /usr/local/share/dotnet/sdk/1.0.3

VS Code version:
C# Extension version: 1.9.0

Steps to reproduce

1. Install c# extension in VS Code on MAC
2. dotnet new console
3. dotnet restore
4. Open in VS CODE

5. Wait for all components to stop downloading and installing, make sure that .NET core debugger is installed properly

   Following is output in "C#" pane

   ```
   Updating C# dependencies...
   Platform: darwin, x86_64

Downloading package 'Mono Runtime (macOS)' (2031 KB) .................... Done!
Downloading package 'Mono Framework Assemblies' (5829 KB) .................... Done!
Downloading package 'OmniSharp (Mono 4.6)' (21963 KB) .................... Done!
Downloading package '.NET Core Debugger (macOS / x64)' (43814 KB) .................... Done!

Installing package 'Mono Runtime (macOS)'
Installing package 'Mono Framework Assemblies'
Installing package 'OmniSharp (Mono 4.6)'
Installing package '.NET Core Debugger (macOS / x64)'

Finished
```

1. create default .NET build task
2. create default .NET debug launch config
3. start debugging session

Expected behavior

Debugging session starts

Actual behavior

I receive error:

The .NET Core Debugger is still being downloaded. See the C# Output Window for more information.

there is no C# output

[tomitrescak]

I can see that the problem is that install.Lock is present in the package directory and this triggers the message. After removing it manually, it complains with Run 'Debug: Download .NET Core Debugger' in the Command Palette or open a .NET project directory to download the .NET Core Debugger.

Trying to run "Debug: Install .NET core debugger" yields to command 'csharp.downloadDebugger' not found.

[EDIT] The build works just fine. Only the debugger is not launched

[gregg-miskelly]

@tomitrescak very strange. If you uninstall and reinstall the extension again, do you get the same behavior?

[tomitrescak]

@gregg-miskelly yes, I tried that several times unfortunatelly. I always get the install success message, but the debugger is not installed and install.lock is left behind.

[gregg-miskelly]

Interesting. No idea what is going on there. If you don't mind doing us a favor, I can send you instructions on how to setup debugging and where to start. Otherwise, I can send you a private with some extra logging to try and understand the problem.

[gregg-miskelly]

I should say: I will not in the office much over the next two days, so it will likely be Monday either way.

[tomitrescak]

@gregg-miskelly I'll gladly follow your instructions, please send them to me.I will also try full reinstall of VS Code. I'm pretty much open to anything ;)

[chuckries]

@tomitrescak Can you please uninstall and reinstall the extension. After reinstalling and seeing the output pane download and install packages, open the developer tools in VS Code by navigating to Help -> Toggle Developer Tools. There may be an error message in the console that can help us. Please report back anything you find.

[gregg-miskelly]

@tomitrescak try this --

First install:

• Node.js (newer than 4.3.1)
• Npm (newer 2.14.12)

Then:

1. git close https://github.com/OmniSharp/omnisharp-vscode.git
2. cd omnisharp-vscode
3. npm i
4. npm run compile
5. Open this directory in VS Code (code . assuming it is on your path)
6. Open src/main.ts
7. Set a breakpoint in the then block for ensureRuntimeDependencies in the activate function
8. F5
9. When the extension host (target) VS Code instance starts, open a .cs file
10. When the breakpoint hits, see if what the value for success is. If it is true, see what in the world is going wrong in coreclrdebug.activate.
11. If you need to start these steps again -- Close the extension host instance, rm .\install.Lock and rm -r .debugger, and go back to step 8.

[badgerowluke]

so I'm having the exact same problem and right now it's looking like I'm getting a Promise.reject of type GitError. The repo it appears to be trying to hit is the one for the *.cs file that I opened to test against. Wouldn't I be expecting it to go back up to omnisharp in this case?

I'm also getting an connection reset error on this: "https://omnisharpdownload.blob.core.windows.net/ext/omnisharp-mono-1.17.0.zip"

[gregg-miskelly]

@fatguyclimbs I am not 100% following what you are saying.

By "I'm having the exact same problem" are you saying that the debugger downloads and installs correctly (you should get the same output in the C# pane that are listed above), but then when you try to debug you get "The .NET Core Debugger is still being downloaded. See the C# Output Window for more information"?

I don't see how a GitError could have anything to do with the debugger installing. My guess is that is unrelated.

[badgerowluke]

@gregg-miskelly my apologies. I put my breakpoint on the wrong .then block. I'

It ended up skipping over both of your if statements in the coreclrdebug.activate method values are included next to the equality check.

!CoreClrDebugUtil.existsSync(_debugUtil.debugAdapterDir())) ==
"/Users/LukeB/Documents/workspace/omnisharp/omnisharp-vscode/.debugger" and
!CoreClrDebugUtil.existsSync(_debugUtil.installCompleteFilePath() == "/Users/LukeB/Documents/workspace/omnisharp/omnisharp-vscode/.debugger/install.complete"

[gregg-miskelly]

@fatguyclimbs: Thanks! What do you get with:

cd /Users/LukeB/Documents/workspace/omnisharp/omnisharp-vscode
ls Install.*

[badgerowluke]

nothing came back from the ls command.

However, running through the debugger seems to have resolved my issue though as I was able to debug through the HttpClient call that's been holding me up since last night.

I'm more than happy to continue to dig through anything if there's anything that is left over that can possibly help from this machine!

[gregg-miskelly]

hmm... Well, you are certain welcome to just carry since you don't have the repro right now. But if you want to try again, you could certainly do a rm .\install.Lock and rm -r .debugger from the root of the OmniSharp-vscode and then try again. If that doesn't get you back into the failing state, git clean -xdf will clean everything out and you can start completely clean. I am a little confused why nothing came back since you should have at least had an install.Lock file.

[badgerowluke]

I found the install.lock file back in the root of ms-vscode-csharp-1.9.0 file back up in /Users/LukeB/.vscode.

but as soon as I get the POC I'm working on running I'll go back and see what else I can dig up.

thanks for the assist

[sebastianteres]

I was having the same issue until I disabled the Legacy C# Support extension and tried again... not sure if that was the problem though.

[CwjXFH]

I was having the same issue:

When i reinstall it ,it still doesn't work.
My OS:Ubuntu 17.04
.NET Core Version:1.0.4

[gregg-miskelly]

@CwjXFH that error message is wrong, but the real problem is likely that Ubuntu 17.04 isn't officially supported. Here is the message you should have received earlier:

logger.appendLine(If '${info.distribution.name}' is binary compatible with a Linux distribution officially supported by .NET Core, you may be able to resolve this by setting 'csharp.fallbackDebuggerLinuxRuntimeId' in 'File->Preferences->Settings' and restarting VS Code.);

[acelot]

I have finally resolve this issue on Ubuntu 17.04!

1. Remove OmniSharp extension from VSCode.
2. Close VSCode.
3. Install dependencies:

sudo apt-get install libunwind-dev libicu-dev

1. Start VSCode.
2. Set csharp.fallbackDebuggerLinuxRuntimeId to value ubuntu.16.10-x64
3. Install OmniSharp extension.
4. Happy debugging!

[prashantquaero]

Is there any update on this issue. Most of the times whenever i open my project in VS Code Omisharp starts downloading

[filipw]

@prashantquaero please remove "omnisharp.path": "latest" from your settings. you are opted into new builds from master so there are new ones multiple times a day