title: How can I prevent the "... has stopped working" window on my Server 2008 R2 dev box?
body: <p>I'm using a Windows Server 2008 x64 R2 machine as a development box.  Amongst many other things I've got Visual Studio 2008 SP1 installed on it.  When I'm working on a project, I sometimes need to use Debug > Start without Debugging (Ctrl + F5).  If the program throws an exception, I get a new R2-style window appear.  I'm pretty sure I didn't see this on my XP box - this is the first time I've developed directly on a server.  Is there any way to avoid this - it's really beginning to bug me?  </p>
  
  <p>E.g. my current project is accessing a WCF service - I'm using Ctrl+F5 to start a console program client.  I run it and get the window.  The title is the name of the project I've just started and it contains:</p>
  
  <pre><code>[insert-project-name-here] has stopped working
  
  Windows can check online for a solution to the problem.
  
  --&gt; Check online for a solution and close the program
  
  --&gt; Close the program
  
  --&gt; Debug the program
  
  V  View problem details.
  </code></pre>
  
  <p>Clicking on "Close the program" will actually close the window and the exception message appears in the console, which is what I want (but without the extra window-faffing).</p>
  
  <p>How can I avoid this annoyance?</p>