title: Visual Studio Breakpoint Warning
body: <p>When debugging my code, I often throw breakpoints in to check the values of local variables to make sure everything is on the right track.</p>
  
  <p>Lately, when I make changes to my code and recompile, all my breakpoints turn into the outline of a circle (instead of a full red circle) and it gives me an error that reads;</p>
  
  <blockquote>
    <p>The breakpoint will not currently be hit. No executable code is
    associated with this line. Possible causes include: conditional
    compilation or complier optimizations.</p>
  </blockquote>
  
  <p>What's strange about this issue is that I can simply remove and add the breakpoint and everything will work completely fine.</p>
  
  <p>I am not using any type of conditional compilation or complier optimizations. Does anyone know what this means or how to fix this? It gets quite annoying replacing 10-12 breakpoints each time I compile.</p>