Skip to content
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

[ERROR]: C# Extension failed to install the debugger package #2265

Closed
RandallFlagg opened this issue May 5, 2018 · 12 comments
Closed

[ERROR]: C# Extension failed to install the debugger package #2265

RandallFlagg opened this issue May 5, 2018 · 12 comments

Comments

@RandallFlagg
Copy link

RandallFlagg commented May 5, 2018

Environment data

dotnet --info output:

.NET Command Line Tools (2.1.4)

Product Information:
Version: 2.1.4
Commit SHA-1 hash: 5e8add2190

Runtime Environment:
OS Name: Windows
OS Version: 10.0.15063
OS Platform: Windows
RID: win10-x64
Base Path: E:\Programs\dotnetCore\current\sdk\2.1.4\

Microsoft .NET Core Shared Framework Host

Version : 2.0.5
Build : 17373eb129b3b05aa18ece963f8795d65ef8ea54

VS Code version: 1.22.2
C# Extension version:
1.14.0

Additional Info

Read the following links:
#991
#994
#1712
dotnet/core#767

The following error shows in devtools:
https://github.com/OmniSharp/omnisharp-vscode/blob/7f128dae95e3281cd49502ed095fbed53a83d6e9/src/coreclr-debug/activate.ts#L79

There should be a normal error indicating what the problem is and maybe even manual steps to fix this.
This happened to me on a few system by now. Every time fixed by luck.
I have removed the extension and reinstalled.
I removed VSCode and reinstalled.
Nothing helped.

Steps to reproduce

Install the C# extension

Expected behavior

Show the steps while installing the extension

Actual behavior

The following error is shown in the console:
[ERROR]: C# Extension failed to install the debugger package

@gregg-miskelly
Copy link
Contributor

gregg-miskelly commented May 5, 2018

@RandallFlagg What I believe this error message means is that for some reason the C# extension thinks it downloaded and extracted all files, but somehow the debugger is missing.

What do you get from:

dir "%userprofile%\.vscode\extensions\ms-vscode.csharp-1.14.0\.debugger\*.exe"
dir "%userprofile%\.vscode\extensions\ms-vscode.csharp-1.14.0\install.Lock"

@RandallFlagg
Copy link
Author

RandallFlagg commented May 5, 2018

I use the portable option(as expliained here) so the directories don't exists where you mentioned.

Regardless of my above saying the "%extentionLocation%\.debugger folder doesn't exist.
The install.Lock file exists.

@gregg-miskelly
Copy link
Contributor

That is definitely why you are seeing this error. Now we need to try and figure out how we got into this state.

If you delete install.Lock and restart VSCode, does the problem happen again? If so, do you get any other logging from the C# extension?

@gregg-miskelly
Copy link
Contributor

@RandallFlagg are you still seeing this problem? Would you like help, or should I close this?

@ptian
Copy link

ptian commented May 18, 2018

I have the same issue. I don't have the .debugger directory in "%userprofile%.vscode\extensions\ms-vscode.csharp-1.15.2" and install.lock does not exist in "%userprofile%.vscode\extensions\ms-vscode.csharp-1.15.2".

@tiomke
Copy link

tiomke commented May 20, 2018

I have the same issue on OS X 10.11.6

@RandallFlagg
Copy link
Author

@gregg-miskelly sorry for the delay. I have found the reasons for this. It happens on 2 different setups I have.

  1. VSCode settings are not in the default location
  2. VSCode settings are behind a symlink. (default location that points to somewhere else)

Can you confirm?

@ptian @tiomke is one of those your setup by any chance?

@ptian
Copy link

ptian commented May 25, 2018

My vscode is installed in "C:\Program Files\Microsoft VS Code" but the settings.json is in C:\Users<user ID>\AppData\Roaming\Code\User. How do I correct it? Thanks.

@jgfoster
Copy link

jgfoster commented Mar 6, 2019

I have this issue on macOS 10.14.3, Visual Studio Code 1.31.1, C# extension version 1.17.1.

@akshita31
Copy link
Contributor

@jgfoster The beta version contains some download validation and might fix the problem. You can install it by following the instructions here. Please let us know if this fixed the issue.

@jgfoster
Copy link

@akshita31, I no longer get an error installing the 1.18.0-beta10. Thanks!

@akshita31
Copy link
Contributor

This issue is fixed in the latest beta(1.18.0-beta10) and the corresponding release(1.18.0) which is scheduled next week. I will close this issue now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants