Raise Events in .NET on the main UI thread

by

Your library could check the Target of each delegate in the event’s invocation list, and marshal the call to the target thread if that target is ISynchronizeInvoke:

private void RaiseEventOnUIThread(Delegate theEvent, object[] args)
{
  foreach (Delegate d in theEvent.GetInvocationList())
  {
    ISynchronizeInvoke syncer = d.Target as ISynchronizeInvoke;
    if (syncer == null)
    {
      d.DynamicInvoke(args);
    }
    else
    {
      syncer.BeginInvoke(d, args);  // cleanup omitted
    }
  }
}

Another approach, which makes the threading contract more explicit, is to require clients of your library to pass in an ISynchronizeInvoke or SynchronizationContext for the thread on which they want you to raise events. This gives users of your library a bit more visibility and control than the “secretly check the delegate target” approach.

In regard to your second question, I would place the thread marshalling stuff within your OnXxx or whatever API the user code calls that could result in an event being raised.

More Related Contents:

  1. lock keyword in C#
  2. If async-await doesn’t create any additional threads, then how does it make applications responsive?
  3. Task vs Thread differences [duplicate]
  4. How to update GUI with backgroundworker?
  5. How to correctly implement a BackgroundWorker with ProgressBar updates?
  6. reference assignment is atomic so why is Interlocked.Exchange(ref Object, Object) needed?
  7. Reliably stop System.Threading.Timer?
  8. Proper way to implement a never ending task. (Timers vs Task)
  9. Is it OK to use a string as a lock object?
  10. Monitor vs lock
  11. EF Data Context – Async/Await & Multithreading
  12. Process queue with multithreading or tasks
  13. Using string as a lock to do thread synchronization
  14. Are empty interfaces code smell? [closed]
  15. Properly locking a List in MultiThreaded Scenarios?
  16. A way of casting a base type to a derived type
  17. Thread Control.Invoke
  18. Strange behaviour of Console.ReadKey() with multithreading
  19. Is .GetAwaiter().GetResult(); safe for general use?
  20. Parallel.ForEach memory usage keeps growing
  21. Why CancellationToken is separate from CancellationTokenSource?
  22. Create multiple threads and wait for all of them to complete
  23. How to correctly read an Interlocked.Increment’ed int field?
  24. Async WebApi Thread.CurrentCulture
  25. Non-virtual interface design pattern in C#/C++
  26. How to create a thread?
  27. Logging to an individual log file for each individual thread
  28. Can somebody explain this odd behavior when working with ThreadPool?
  29. Calling TaskCompletionSource.SetResult in a non blocking manner
  30. Using WebBrowser in a console application

Leave a Comment