The Breakpoint will not currently be hit. No symbols where loaded for this document

Question

Windows 8, VS2013 IIS8,5

I'm trying to connect to a local WEB API by connecting to processes w3pv.exe (Managed (v4.0.30319), 19). The website front end and back end is both running fine on my local IIS. Right after publishing my x86 web API to the local IIS i try to connect to the process, where the break point states "The Breakpoints will not currently be hit. No symbols where loaded for this document". My colleague' can without any problems debug from his local computer.

So far I have.

1. Reinstalled VS2013.

2. Checked All Debug Properties

   -Project -> build: Define DEBUG constant check / Define TRACE constant check.

   • Generate serialization assembly = Auto. Advanced build settings -> Debug info = full
   • Enable Just My Code: Check, Use Managed Compatibility Mode: Check
   • Enable Edit and Continue : Check

3. Made sure all Debug mode is set and all project Configured to Active solution platform x86, marked Debug and Build.

4. Deleted all bin and obj folders, as well as pdb folder in C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\Temporary ASP.NET Files

5. Reset IIS.

6. Set Select Code Type to Automatically determine the type of code to debug

7. Checked in IIS that .Net compilation -> Debug and Enable Prefetch is set to true.

And I still get the same error message. Anyone found anything in addition to this?

Answer 1

I have encountered similar problems many times while training new employees in our very complicated devenv, so here is our internal step by step instruction:

1. Don't panic
2. Make sure you attached the debugger to the correct process - you debug the plugin by launching VMS which is external app that has separate config file where the plugin path is stored, so when you change just your configuration Debug/Release it doesn't work.
3. Make sure you have symbols generated for the assembly Project properties->Build->Advanced->Output section
4. Make sure the build path hasn't changed. You may have accidentally changed the path and you may only think that the assembly you are trying to debug is the correct one.

Investigating the information you provided this is only help I can think of. My guess is the files you publish are not the files you're debugging locally.

Answer 2

RESOLVED (embarrassed)

A few day's ago, I downloaded the front-end code for the website from the VPN (GIT). I forgot to update the code-behind reference in the App.js file in the front end root. This, of course, referred to the API on the cloud, and not my local API.

This took me way to long to find out. But, at the same time, it's not a solution I've seen so far on the web.

Thanks for all your help.