Omnisharp-vscode: Debugger doesn't work, looking for nuget.config

[sebastienros]

When starting vscode it complains the debugger can't be loaded because it can't find [my_app_local]\.vscode-insiders\extensions\ms-vscode.csharp-1.0.1-rc2\nuget.config.
It's actually looking for the one in \.vscode-insiders\extensions\ms-vscode.csharp-1.0.1-rc2\coreclr-debug so it works when I copy it and restart vscode.

Repro steps:

• download vscode march insider version
• download omnisharp-vscode release 4/8
• open an existing dotnet project folder
• displays an error message stating Debugger could not be loaded, with the nuget.config explanation in the log

[gregg-miskelly]

What version of .NET CLI do you have? (dotnet --info)

[gregg-miskelly]

Thanks, @jeffpapp and @joaomello you are running into a different problem than sebastienros. I moved your issue to #181.

[sebastienros]

1.0.0-beta-002279

[chuckries]

Are you on windows? Have you fully uninstalled all previous dotnet CLI's from Add/Remove Programs?

[chuckries]

I was not able to repro this on my machine with

c:\Users\chuckr\Source\scratch>dotnet --info
.NET Command Line Tools (1.0.0-beta-002279)

Product Information:
 Version:     1.0.0-beta-002279
 Commit Sha:  76610c4cd4

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.10586
 OS Platform: Windows
 RID:         win10-x64

and

[Window Title]
Visual Studio Code - Insiders

[Main Instruction]
Visual Studio Code - Insiders

[Content]

Version 0.10.15-insider
Commit 67567498285c2081312077cc24370d97676fc20a
Date 2016-04-11T10:56:21.409Z
Shell 0.35.6
Renderer 45.0.2454.85
Node 4.1.1

[OK]

We have seen issues similar to this when the .net cli install gets into a bad state. I would try uninstalling any and all CLI's and then installing 1.0.0-beta-002279 from here. In Add/Remove Programs, make sure you sure for dotnet, .net, net, and cli just to make sure you spot any old version sticking around.

[sebastienros]

Ok, I will assume this is just my machine then, as I get the CLI from aspnet core builds automatically and also from the MSI in Program Files ...