Handle the exception in the usual way (Try/Catch). From there on in, it's
up to you what to do with it. Either yes, pass the error state back to the
client via. a delegate, or handle the error in the thread itself.
Personally, I use a delegate to tell the form what the error was and then
idle the thread (but ensuring no state was changed; in my case, by rolling
back a database transaction). The client form can then decide whether to
retry the operation (if it was cancelled due to deadlock for example) or
whether to just tell the user (a simple message box).
"Bob" <no***@nowhere.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
Is there some built-in way of handling exceptions thrown inside a thread,
or
do I need to pass exception conditions to a delegate (which would force me
to handle all exceptions in the thread itself)?
TIA,
Bob
