title: Visual Studio 2012 - Breakpoints in Razor view files (".cshtml") not being loaded
body: <p>When setting a break point in a razor view (".cshtml") the circle which is normally red turns to a red hollow circle when the debugger is started. When hovering over the hollow circle it displays the following:</p>
  
  <blockquote>
    <p>The breakpoint will not currently be hit. No symbols have been loaded for this document</p>
  </blockquote>
  
  <p>It's only razor view files, with normal ".cs" files there are no problems.</p>
  
  <p>There are a lot of other questions which have proposed solutions for the same "error" message as above but none has actually worked. What I have tried:</p>
  
  <ul>
  <li>Cleaning the solution</li>
  <li>Ensuring that in the properties -> Web window, under the "debugger" section that ASP.NET is checked</li>
  <li>Ensuring that in the properties -> Build window, that both Define DEBUG and TRACE are checked and in the output section of the same window, clicking the advanced button, the debug info is set to "Full"</li>
  <li>Rebuilding everything a million times.</li>
  <li>Using VS with administrator rights (I do that normally anyway)</li>
  <li>Restarting system</li>
  <li>Restarting site in IIS</li>
  <li>Ensuring that the Active Solution Configuration is set to Debug</li>
  <li>Checked that in the web.config file, compilation debug="true"</li>
  </ul>
  
  <p><strong>Edit:</strong> I'm referring to the razor code of course, not html or even javascript. E.g. setting a break point in a foreach loop in razor</p>
  
  <p><strong>Edit2</strong>: I'm able to step through the razor code if I set a breakpoint in a controller, as the the debugger will go through the view before being "done". I'm still not able to actually set breakpoints in razor view files though. The hollow circle is still showing and it won't get hit. </p>
  
  <p><strong>Edit3</strong>: Killing the "IIS Working Process" which points to w3wp.exe temporary solved the problem. I was able to debug razor views again. A few hours later, the same problem again.</p>