C#

From MSDN:

When a thread other than the creating thread of a control tries to access one of that control's methods or properties, it often leads to unpredictable results. A common invalid thread activity is a call on the wrong thread that accesses the control's Handle property. Set CheckForIllegalCrossThreadCalls to true to find and diagnose this thread activity more easily.

Tech, life, family, faith: Give me a visit.
I'm currently blogging about: Goof around music jam with my brothers (with video)
The apostle Paul, modernly speaking: Epistles of Paul

Judah Himango

class MyCrazyLib
{
   private SynchronizationContext syncContext;
   public event EventHandler WorkProgressed;

   public MyCrazyLib(SynchronizationContext eventRaisingSync)
   {
      this.syncContext = eventRaisingSync;
   }

   void DoWorkInBackground()
   {
      ThreadPool.QueueUserWorkItem(MyWorkMethod);
   }

   void MyWorkMethod(object state)
   {
      // Pretend we do some work here...
      ...

      // Now raise the event using our synchronization context.
      this.syncContext.Post(delegate(object state)
      {
         this.WorkProgressed(someSender, EventArgs.Empty);
      });
   }
}

// While on the UI thread.
MyCrazyLib lib = new MyCrazyLib(WindowsFormsSynchronizationContext.Current); // We want to raise events on the current UI thread
lib.WorkProgressed += MyHandler;
lib.DoWorkInBackground();

...

void MyHandler(object sender, EventArgs e)
{
   // This will be called on the UI thread! No Invoke required. :)
}

Tech, life, family, faith: Give me a visit.
I'm currently blogging about: Goof around music jam with my brothers (with video)
The apostle Paul, modernly speaking: Epistles of Paul

Judah Himango