Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Visual Studio 2010 debug not starting, F5 or click on "Play" not working, not doing anything. Waiting 2-3 minutes solves the issue

I have a relatively simple C# (Framework 4) console application. When I click the "Play" icon or hit F5 (i.e. start the program in debug mode), the icon becomes gray for a second, then goes back to green, but nothing happens. If I wait 2 or 3 minutes and try again, the debug session starts up normally, breakpoints are hit and everything.

Things I have tried without success:

  • Cleaning the solution, then rebuilding.
  • Renaming the output assembly.
  • Restarting Visual Studio.

The only thing that works is just waiting. I don't see any related processes still running during these 2-3mins (svchost, conhost, *.vshost or cmd).

like image 780
Diego Avatar asked May 23 '11 21:05

Diego


People also ask

How do I enable debugging in Visual Studio?

In the Visual Studio toolbar, make sure the configuration is set to Debug. To start debugging, select the profile name in the toolbar, such as <project profile name>, IIS Express, or <IIS profile name> in the toolbar, select Start Debugging from the Debug menu, or press F5.

What is Ctrl F5 in Visual Studio?

F5 is used to start your project in debug mode and Ctrl-F5 is used to start your project without debug mode.

How do I open Debug console in Visual Studio?

Press F5 to run the program in Debug mode. Another way to start debugging is by choosing Debug > Start Debugging from the menu. Enter a string in the console window when the program prompts for a name, and then press Enter . Program execution stops when it reaches the breakpoint and before the Console.


2 Answers

try this: open Task Manager, go to processes tab and look for process named after your app. if its there just kill the bastard and try to debug again. for me it worked like miracle

like image 173
Loki Avatar answered Sep 19 '22 06:09

Loki


I've seen this problem when my network connection is flakey and I've set the debugger to automatically download symbols from Microsoft's symbol server. It tries for a long time, then times out, then life proceeds. There should be clues in the Output window (where it normally lists all the modules being loaded and whether it got symbols for them).

like image 21
Adrian McCarthy Avatar answered Sep 21 '22 06:09

Adrian McCarthy