Debugging doesn't start [closed]

Answer 1

With regard to the problem above where the Console doesn't appear. (I don't have enough merit points to comment directly against that post.)

I disabled the hosting process in order to get around the problem of it being left running and leaving the files locked. When I did this I found my Console window no longer appeared when I hit F5 to debug, although my program ran fine. I then noticed that I had the "Prefer 32-bit" check-box ticked. I unticked this, rebuilt and the Console window appeared once more. This seemed strange so I ticked it off again and confirmed I can reproduce this behaviour. I'm using Visual Studio 2013.

Answer 2

Same error, tried executing VS as Administrator and it worked.

Answer 3

Restart VS and try to debug. Some time it happens, even I also had the same problem.

Answer 4

Quick fix that might help someone:

I am using VS2013 and my debugger suddenly stopped working. I kept getting a message box stating debugging is not supported.

I finally fixed it by clearing NATIVE checkbox under Debuggers in the Property Pages->Start Options tab for the start up project. I now only have ASP.NET selected under Debuggers.

Answer 5

I have found a solution:

1. Close your Visual studio solution
2. Open your .csproj project header with notepad ++ for example.
3. Search for <UseIISExpress>false</UseIISExpress> in the <PropertyGroup> section
4. Change the value to true : <UseIISExpress>true</UseIISExpress>
5. Save
6. Open your solution and for me now debug works on my project

Answer 6

I had this problem in a WPF application I was working on. When running the debugger, a process named MyApp.VsHost.exe would start and continue running in the background, but there would be no exceptions thrown and nothing in the Output window except build information.

It was because I had changed the namespace of my App class but did not update the Class attribute in App.xaml to match the new namespace. I changed the namespace in the xaml file and it worked again.