-
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
ASP.NET Debugging No Longer Working #541
Comments
Hi, exactly the same thing happening to me. |
@ruicraveiro What is the CSharp extension version you are using? |
Hi Cagri, I'm using 1.2.2. Any other information you might need, please ask. |
When trying to run using .net core launch, I get exactly the same error as Weinand's. Adding to that, on the extension output I get: waiting for v8 protocol on stdin/stdoutwaiting for v8 protocol on stdin/stdout. I also tried to run the app via command line and attach the debugger to it. When attaching it also fails, but this time, the message I get is one of those popups saying "Debug adapter process has terminated unexpectedly". I also get a message in the extension log saying: waiting for v8 protocol on stdin/stdoutwaiting for v8 protocol on stdin/stdoutwaiting for v8 protocol on stdin/stdout |
@ruicraveiro, the same scenario doesn't reproduce here for us, so we will need to see what's going on from the logs. Can you add the following in your launch.json configuration: "logging" : { and send us what you get in the debug console? (You can send to [email protected] if you prefer) There must be an error we are running into before the ObjectDisposedException error. |
Here goes (with some paths replaced by [undisclosed]: 1: (487) LaunchOptions<LocalLaunchOptions xmlns='http://schemas.microsoft.com/vstudio/MDDDebuggerOptions/2014' |
@ruicraveiro it looks like your app is referencing RC2 runtime. CSharp extension no longer supports debugging that. Is it possible for you to move to RTM and try again? |
Hi Cagri, that was the problem. Everything's working now. Thanks! |
Excellent, let us know if you run into further issues. |
I completely updated all my project.json dependencies to the latest versions (mostly 1.0.0 now!) and as well followed the instructions here: https://docs.efproject.net/en/latest/miscellaneous/rc2-rtm-upgrade.html#net-core-remove-imports-in-project-json It took a while, but I got everything working again! |
From @robbpriestley on July 8, 2016 2:29
Steps to Reproduce:
I re-installed .NET Core just to be on the safe side--no difference. I was already running the latest version. I also noticed after I installed the new version of VS Code that a background process re-installed the debug module (? details hazy--I just saw it on the status bar on the bottom of the screen).
Copied from original issue: microsoft/vscode#8879
The text was updated successfully, but these errors were encountered: