dotnet restore fails with bogus missing config file error on some computers

Moving issue from https://github.com/OmniSharp/omnisharp-vscode/issues/96

Steps to reproduce

1. Install VS Code on a Ubuntu

2. Try to restore the CLR debugger in the same way that VS Code will –

   cd ~/.vscode/extensions/ms-vscode.csharp-0.3.7/coreclr-debug dotnet --verbose restore --configfile NuGet.config

Expected behavior

Restore succeeds

Actual behavior

On some machine, restore fails with –

~/.vscode/extensions/ms-vscode.csharp-0.3.7/coreclr-debug$ dotnet --verbose restore --configfile NuGet.config
error: File '/home/dhanajay/.vscode/extensions/ms-vscode.csharp-0.3.7/NuGet.config' does not exist.

NOTES:

1. The error message at least indicates that dotnet restore is looking in the wrong directory (the current directory is …\coreclr-debug)
2. We had someone internal run into this on OSX. That time it turned out to be due to junk left over from an older version. But @dhnnjy tried uninstalling/reinstalling with no success.

Environment data

dotnet --version output: .NET Command Line Tools (1.0.0-beta-001675)

Product Information: Version: 1.0.0-beta-001675 Commit Sha: N/A

Runtime Environment: OS Name: ubuntu OS Version: 14.04 OS Platform: Linux Runtime Id: ubuntu.14.04-x64

[mightea]

I have a similar issue on OS X 10.11.4. I reinstalled VS Code (deleted the app and the ~/.vscode folder). The issue persists.

Actual Behavior

Downloading and configuring the .NET Core Debugger...
Running /usr/local/share/dotnet/bin/corerun "/usr/local/share/dotnet/bin/NuGet.CommandLine.XPlat.dll" "restore" "--configfile" "NuGet.config" "--runtime" "osx.10.11-x64"
Process ID: 6489
Specify --help for a list of available options and commands.
error: Unrecognized option '--configfile'
dotnet exited with error code 1
Error while installing .NET Core Debugger.

Environment Data

.NET Command Line Tools (1.0.0)
Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.11
 OS Platform: Darwin
 Runtime Id:  osx.10.11-x64

[blackdwarf]

Thanks @gregg-miskelly I will close this down then. We can reopen on NuGet/Home if it surfaces again.