"Jon Skeet [C# MVP]" <skeet@pobox.com> wrote in message
news:MPG.224cec489d1e9fb3ba9@msnews.microsoft.com...
> It would help if you'd say what you're trying to do with the message
> when you get the exception.
>

Relaxin <me@yourhouse.com> wrote:
> How do you handle the cross-thread issues if you don't have a UI?
>
> I'm writing a class that's using the MSMQ and MSMQ notifies the class when a
> new message has arrived.
> But it notifies you on a new thread.
>
> I need to notify a class on the main thread that a new message has arrived,
> but I get the cross-thread exception.
>
> I've tried many different things, including delegates, but I still get this
> error.
>
> All of my googling turns up ways to handle it if you have a UI, which I
> don't.

Relaxin <me@yourhouse.com> wrote:
> "Jon Skeet [C# MVP]" <skeet@pobox.com> wrote in message
> news:MPG.224cec489d1e9fb3ba9@msnews.microsoft.com...
> > It would help if you'd say what you're trying to do with the message
> > when you get the exception.
>
> I'm not be anything with the message, I'm just trying to notify the calling
> program, thru a delegate, that a message has arrived.

> So do you know anything about Cross-Thread exceptions at all and can offer
> some help?

"Jon Skeet [C# MVP]" <skeet@pobox.com> wrote in message
news:MPG.224d27adb23c5bd5bab@msnews.microsoft.com...
> Relaxin <me@yourhouse.com> wrote:
>> "Jon Skeet [C# MVP]" <skeet@pobox.com> wrote in message
>> news:MPG.224cec489d1e9fb3ba9@msnews.microsoft.com...
>> > It would help if you'd say what you're trying to do with the message
>> > when you get the exception.
>>
>> I'm not be anything with the message, I'm just trying to notify the
>> calling
>> program, thru a delegate, that a message has arrived.
>
> And how are you doing that? What call is throwing the exception? What's
> the calling program doing?
>

Relaxin wrote:

> How do you handle the cross-thread issues if you don't have a UI?

Relaxin <me@yourhouse.com> wrote:
> I'm doing it thru a delegate like I said!
> The delegate is throwing the exception, can't you see that!
> Waiting for the delegate notification just like I explained!
>
> WOW!
> I guess they give MVP's to anyone!
>
> What a moron!
>
> Bye...and of course, I don't need your type of help, so I'm now done
> with you.
>
> Good Day...

"Jon Skeet [C# MVP]" <skeet@pobox.com> wrote in message
news:MPG.224df6cb10eeb905baf@msnews.microsoft.com...
> Good luck waiting for help if you're not going to give any more
> information.
>
> I'll be busy helping people who are actually willing to explain their
> situation in more detail.
>

"Barry Kelly" <barry.j.kelly@gmail.com> wrote in message
news:lih7u3l34dp5jpe6sf3b0gc08jmtu81m4h@4ax.com...
> Relaxin wrote:
>
>> How do you handle the cross-thread issues if you don't have a UI?
>
> You need a synchronization point. You can't hijack a random thread and
> have it pay attention to you; it needs to wait explicitly at some point
> so that you can communicate with it.
>
> Apps with UIs have a synchronization point for the main thread in the
> form of the message loop. The message loop waits for messages. Other
> threads can communicate with it by sending a message. Control.Invoke
> works by doing this.
>
> For apps without UIs, you need to set up the synchronization point
> yourself. You can do that by implementing a message loop, or a
> producer-consumer queue (Google that - there's a trivial textbook
> implementation possible using monitors, often one of the first things
> taught in college courses when threading is first discussed), or other
> methods of cross-thread communication. For example, the main thread
> could block until a background thread wakes it up, using e.g.
> ManualResetEvent or monitors (Monitor.Wait, Monitor.Pulse, etc.).
>