title: Debug.Fail gives me a "Dispatcher processing has been suspended" error
body: <p>I had a problem in code that caused a Debug.Fail to be called. I use Debug.Assert and Debug.Fail quite a lot, since it not only gives me instant notification that a problem exists, but also information about what and where the problem is located.</p>
  
  <p>But this time the Debug.Fail itself caused an even bigger problem, since the UI (WPF) froze becuse of the following error:</p>
  
  <blockquote>
    <p>Dispatcher processing has been suspended, but messages are still being processed.</p>
  </blockquote>
  
  <p><strong>Is there anything I can do to make Debug.Fail succeed?</strong> I most definitely do not want to have code around by Debug.Fail to check whether to Invoke or BeginInvoke.</p>
  
  <p><strong>EDIT:</strong> I suppose replacing the DefaultTraceListener would do the trick?</p>