I've written an assertion method Ensure.CurrentlyOnUiThread(), below, that checks that the current thread is a UI thread.
Ensure.cs
using System.Diagnostics; using System.Windows.Forms; public static class Ensure { [Conditional("DEBUG")] public static void CurrentlyOnUiThread() { if (!Application.MessageLoop) { throw new ThreadStateException("Assertion failed: not on the UI thread"); } } }
Don't use
if(Dispatcher.CurrentDispatcher.Thread == Thread.CurrentThread) { // Do something }
Dispatcher.CurrentDispatcher
will, if the current thread do not have a dispatcher, create and return a new Dispatcher
associated with the current thread.
Instead do like this
Dispatcher dispatcher = Dispatcher.FromThread(Thread.CurrentThread); if (dispatcher != null) { // We know the thread have a dispatcher that we can use. }
To be sure you have the correct dispatcher or are on the correct thread you have the following options
Dispatcher _myDispatcher; public void UnknownThreadCalling() { if (_myDispatcher.CheckAccess()) { // Calling thread is associated with the Dispatcher } try { _myDispatcher.VerifyAccess(); // Calling thread is associated with the Dispatcher } catch (InvalidOperationException) { // Thread can't use dispatcher } }
CheckAccess()
and VerifyAccess()
do not show up in intellisense.
Also, if you have to resort to these kinds of things its likely due to bad design. You should know which threads run what code in your program.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With