Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

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

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 break points in debug mode for any project exect the main project selected as the Startup project in the Project Properties page. I used to be able to click on the other projects and just choose Debug -> Start New Instance. I am getting the error The breakpoint will not currently be hit. No symbols have been loaded for this document. I have tried a lot of things found on Google including:

  • Clean/Rebuild
  • Delete the OBJ and BIN folder form the projects
  • Did VS repair
  • Rebooted
  • Uninstalled/Reinstalled
  • Confirmed Define DEBUG constraint is enabled for Properties -> Build
  • Confirmed Optimize Code is unchecked for Properties -> Build
  • Confirmed Properties -> Build => Platform target was set to Any CPU for all projects
  • Tried running VS using "Run as Administrator"
  • Deleted all the files in /AppData/Local/Temp/Temporary ASP.Net Files/
  • Made sure Debug -> Attack to Process -> Select had "Automatically determine the type of code to debug" was selected
  • Made sure the Properties -> Web -> Debuggerts had ASP.Net checked (my properties has ASP.NEt and Enable Edit and Continue Checked, Natvie Code SQL Server and Silverlight unchecked)
  • Confirmed Target framework in Properties -> Application was set to the same version (4.6) as in the Web.Config/App.Config files.

So what am I missing here? Why can I no longer debug the other projects?

over 4 years ago · Santiago Trujillo
3 answers
Answer question

0

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"
over 4 years ago · Santiago Trujillo Report

0

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.

over 4 years ago · Santiago Trujillo Report

0

My situation was that I have enabled "Optimize code" in the project properties.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!