Home/ Questions/Q 6812887
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T20:30:15+00:00

I had a problem in code that caused a Debug.Fail to be called. I

  • 0

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.

But this time the Debug.Fail itself caused an even bigger problem, since the UI (WPF) froze becuse of the following error:

Dispatcher processing has been suspended, but messages are still being processed.

Is there anything I can do to make Debug.Fail succeed? I most definitely do not want to have code around by Debug.Fail to check whether to Invoke or BeginInvoke.

EDIT: I suppose replacing the DefaultTraceListener would do the trick?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Debug.Fail will by default use the DefaultTraceListener. Using ILSpy, I could see that DefaultTraceListener.Fail makes a call to AssertWrapper.ShowAssert. To get around the problem, replace the DefaultTraceListener with your own that has Dispatcher guards around the call to AssertWrapper.ShowAssert.

    Voila! Now you can call Debug.Assert and Debug.Fail without bothering about dispatcher issues.

    • 0