-
Notifications
You must be signed in to change notification settings - Fork 676
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
debugger always fails to "restore" #169
Comments
The latest builds of the .NET CLI aren't compatible with the version of the C# extension currently in the gallery. So you will either need to install a newer build of the C# extension, or go back to the 'beta' build of the CLI referenced from http://dotnet.github.io/getting-started. Instructions for the getting-started builds: https://github.com/OmniSharp/omnisharp-vscode/blob/master/debugger.md |
I have the best newest version of the C# extension.
|
The newest**
|
@ceil you have 1.0.1-rc? The output above looks to be from the latest version from the VS Code Gallery. |
If you do have 1.0.1-rc, please copy/paste the output from the coreclr-debug output pain. |
So that isn't the latest build? Where do I get a newer one, then? |
As I said -- http://aka.ms/vscclrdogfood |
Sorry. That part got chopped off on the email from my phone. I'll take a look at it momentarily. |
Yes, that did seem to resolve the problem. Thank you very much. |
From @ciel on April 8, 2016 21:13
0.10.11
Windows 10x64
Steps to Reproduce:
cmd
orPowerShell
)dot net new
and hitENTER
to create a new project.Windows Explorer
) and selectOpen with VS Code
The
OUTPUT
window appears and spouts off a lot of attempts to pull in files, and then yields an error; it is different each time for me.Copied from original issue: microsoft/vscode#5107
The text was updated successfully, but these errors were encountered: