Upgrade to Visual Studio 2015 and now can't hit break points in debugging

Question

I have a multi-project solution that I was building in Visual Studio 2013 and it was working fine but now that I have upgraded to Visual Studio 2015 I can no longer hit brea

Answer 1

Running the VS command prompt as admin as running the command: devenv /setup fixed this for me.

Answer 2

The debugger wasn't hitting breakpoints for my ASP application after migrating from my old system to my new system. I forgot to configure in IIS for debugging.

To configure IIS for debugging:

• Sites > MyWebsite
• IIS > ASP > Debugging Properties
  • Set Enable Client-side Debugging to True
  • Set Enable Server-side Debugging to True

Answer 3

In my case I was unable to debug because I had breakpoint set in source control temporary file while analyzing file history instead of actual file in solution.

Answer 4

I had a similar problem, when I created a new build configuration. After hunting around settings in VS2015, I noticed that there were no *.pdb files in my build output. Obviously, debugging would not work if there were *.pdb files.

The fix for me was to go into every project's properties -> 'build' page -> click the "advanced" button at the bottom of the page -> In the dialog's 'Output' section, I set "debug info" to equal "full".

Basically, I created a new solution and project and copied all the build properties into the solution that the debugger was not stopping at break points anymore. In addition to the setting above, I also changed the following setting to match the default debug settings:

• I set on the same advanced page "Internal Compiler Error Reporting" to "prompt"
• In the main 'build' page, I checked in the 'general' section "Define DEBUG constant" and "Define TRACE constant"

Answer 5

I solved this problem when checked Options->Debugging->General->Suppress jit optimization on module load. Before I did that I have also unchecked Tools->Options "Projects and Solutions" "Build and Run" "Only build startup projects and dependencies on run". Don't know if that has any reason why it works after suppress jit is unchecked.

Answer 6

In my case I just changed the setting of my running mode.

Before, I used "release" running mode:

And now, I'm using "debug" running mode: