title: Does Debugger.Break have any side effects?
body: <pre><code>System.Diagnostics.Debugger.Break(); // this DB call has not been mocked
  </code></pre>
  
  <p>I'd like to place these in code at the site of I/O calls to let unit test developers know when they haven't properly mocked out the call, but I don't want to create new problems.</p>
  
  <ol>
  <li><p>Does calling Debugger.Break() have any impact when compiled as Release?</p></li>
  <li><p>Does it have any impact when executing a Debug build but not debugging?</p></li>
  </ol>