title: Program crashes, but Debug Diag says it's a first chance exception, is that correct?
body: <p>Probably this is a normal situation, but I am confused.</p>
  
  <p>I am running my C# Debug application from Visual Studio.  DebugDiag is set up to attach to the process automatically.</p>
  
  <p>I have a rule to collect crash dumps from this application, and the rule defines that the action for unconfigured first chance exceptions should be "none".</p>
  
  <p>But when the application crashes, and when I look at the dump files it says that there is a first chance exception. </p>
  
  <p>From the answer to <a href="https://stackoverflow.com/questions/564681/what-is-a-first-chance-exception">this SO question</a>, I understand that "exceptions are thrown to the debugger first and then to the actual program where if it isn't handled it gets thrown to the debugger a second time"</p>
  
  <p>So why does DebugDiag collect dump files for the first chance exception?</p>
  
  <p>EDIT
  Just to be clear, I am not trying to fix broken code here.  I'm trying to understand why  DebugDiag told me that a first chance exception had made my code crash.  Surely by definition, only a 2nd chance exception can make code crash, i.e. one that has NOT been handled by the code?</p>
  
  <p>"crash" means that the process terminated and DebugDiag generated crash dump files.  I was running the Debug version of the code on "Start without Debugging"</p>