multithreading - In C# what is the recommended way of passing data between 2 threads?

Question

I have my main GUI thread, and a second thread running inside it's own ApplicationContext (to keep it alive, even when there is no work to be done). I want to call a method on my 2nd thread from my GUI thread, but if I just call thread.Method(); it seems to be running on my main GUI thread and causes my GUI to become unresponsive. What is the best way to call methods on different threads?

Update: What I'm really looking to do here is communicate between 2 threads, not communicate with a GUI. The GUI just happens to be one of the threads that will need to communicate with my 2nd thread.

Update #2: Ok, I must really be missing something. I created an event and a delegate and had my worker thread subscribe to the event. But when I call Invoke(MyEvent); from my GUI thread the work that the worker thread does ends up being on the GUI thread and hangs the GUI thread until it's done processing. Is what I'm trying to do even possible, without polling on a static object?

Answer 1

Wow, I can't believe how may people didn't bother reading the question.

Anyways, this is what I do.

1. Create you "message" classes. This stores all the information you want to share.
2. Create a Queue<T> for each thread. Use a SyncLock (C# lock) to read/write to it.
3. When you want to talk to a thread, send it a message object with a copy of all the information it needs by adding the message to the queue.
4. The worker thread can then read from the queue, reading and processing each message in order. When there are no messages, simply sleep.

Make sure that you don't share objects between the two threads. Once your GUI thread sticks a message in the Queue, the GUI thread no longer owns the message. It cannot hold a reference to the message, or you will get yourself into trouble.

This won't give you the best possible performance, but it will be good enough for most applications. And more importantly, it will make it much harder to make a mistake.

UPDATE: Don't use a SyncLock and Queue. Instead use a ConcurrentQueue, which will handle any locking automatically for you. You'll get better performance and are less likely to make a mistake.