Re: Delegate.BeginInvoke and EndInvoke.

Well then I don't see how this approach helps me out then. My motivation
for doing this was to not get tied up when my call to
SystemParametersInfo doesn't return as per my previous thread.

(No WM_SETTINGCHANGE message received by my windows as verified by
spy++)

If this delegate never returns in this case, then won't I have one
thread in the pool that will just hang? Is there no way to terminate
this delegate after the time out period?

=20

-----Original Message-----
From: Discussion forum for developers using Windows Forms to build apps
and controls [mailto:[email protected]] On Behalf Of
Peter Ritchie
Sent: Tuesday, January 15, 2008 12:25 PM
To: [email protected]
Subject: Re: [DOTNET-WINFORMS] Delegate.BeginInvoke and EndInvoke.

The delegate doesn't time out, the code waiting for the asynchronous
delegate times out (i.e. the code calling WaitOne()).  Despite that
"time- out" the delegate is sill running and will call the AsynCallback
when it's done.

The information contained in this e-mail message is PRIVATE. It may =
contain confidential information and may be legally privileged. It is =
intended for the exclusive use of the addressee(s). If you are not the =
intended recipient, you are hereby notified that any dissemination, =
distribution or reproduction of this communication is strictly =
prohibited. If the intended recipient(s) cannot be reached or if a =
transmission problem has occurred, please notify the sender immediately =
by return e-mail and destroy all copies of this message.=20
Thank you.=20