title: How do I fix this error "The breakpoint will not currently be hit. No symbols have been loaded for this document."
body: <p>When trying to debug any of my projects in my solution, none of the breakpoints gets triggered, and I get the following warning message:</p>
  
  <blockquote>
    <p>The breakpoint will not currently be hit. No symbols have been loaded
    for this document.</p>
  </blockquote>
  
  <p>It seems to be specific to this solutions, which consists of 6 projects. A week ago this was still working.</p>
  
  <p>I have tried the folowing:</p>
  
  <ol>
  <li>Enabling/Disabling "Enable Just My Code". </li>
  <li>Cleaned and rebuilt the entire solution. </li>
  <li>Cleaned and rebuilt each project individually. </li>
  <li>Deleted the Bin and Obj folders in each project, and rebuild. </li>
  <li>Cleared the "SymbolCache" folder, and rebuild. </li>
  <li>Repaired and Updated Visual Studio 2017 (Community Edition).</li>
  <li>Updated all packages in the solution. </li>
  <li>Checked that all my projects are set to Debug and Any CPU.</li>
  </ol>
  
  <p>I double-checked that there are no build errors in any of the projects. The application, in general, works fine.</p>
  
  <p>I've tried many solutions I found in forums. The one thing I did notice, is that the Crystal Reports modules have a status message of <code>Cannot find or open the PDB file</code> next to all the DLL's. for example:</p>
  
  <blockquote>
    <p>CrystalDecisions.CrystalReports.Engine.dll
    CrystalDecisions.CrystalReports.Engine.dll    C:\Windows\assembly\GAC_MSIL\CrystalDecisions.CrystalReports.Engine\13.0.3500.0__692fbea5521e1304\CrystalDecisions.CrystalReports.Engine.dll
    No    No  Cannot find or open the PDB file. 72    13.00.21.2533   2017/08/31 02:10 PM 0BCD0000-0BD30000   [15568] iisexpress.exe  [2]
    /LM/W3SVC/2/ROOT-1-132102498773678728</p>
  </blockquote>
  
  <p>I tried uninstalling Crystal Reports, and commenting any code or references to these DLL's. This makes no difference.</p>
  
  <p>The strange thing is that when I open other solutions, the debugger works fine.</p>
  
  <p>Any help or suggestions would be greatly appreciated.</p>