WaitHandle.SignalAndWait Method (WaitHandle, WaitHandle, Int32, Boolean)
Assembly: mscorlib (in mscorlib.dll)
public static bool SignalAndWait ( WaitHandle toSignal, WaitHandle toWaitOn, int millisecondsTimeout, bool exitContext )
public static boolean SignalAndWait ( WaitHandle toSignal, WaitHandle toWaitOn, int millisecondsTimeout, boolean exitContext )
public static function SignalAndWait ( toSignal : WaitHandle, toWaitOn : WaitHandle, millisecondsTimeout : int, exitContext : boolean ) : boolean
The WaitHandle to signal.
The WaitHandle to wait on.
An integer that represents the interval to wait. If the value is Timeout.Infinite, that is, -1, the wait is infinite.
true to exit the synchronization domain for the context before the wait (if in a synchronized context), and reacquire it afterward; otherwise, false.
Return Valuetrue if both the signal and the wait completed successfully, or false if the signal completed but the wait timed out.
toSignal is a null reference (Nothing in Visual Basic).
toWaitOn is a null reference (Nothing in Visual Basic).
The method is called on a thread that has STAThreadAttribute.
This method is not supported on Windows 98 or Windows Millennium Edition.
toSignal is a semaphore, and it already has a full count.
millisecondsTimeout is a negative number other than -1, which represents an infinite time-out.
The wait completed because a thread exited without releasing a mutex. This exception is not thrown on Windows 98 or Windows Millennium Edition.
The WaitHandle cannot be signaled because it would exceed its maximum count.
If millisecondsTimeout is zero, the method does not block. It tests the state of the toWaitOn and returns immediately.
The exitContext parameter has no effect unless the SignalAndWait method is called from inside a nondefault managed context. This can happen if your thread is inside a call to an instance of a class derived from ContextBoundObject. Even if you are currently executing a method on a class that does not derive from ContextBoundObject, like String, you can be in a nondefault context if a ContextBoundObject is on your stack in the current application domain.
When your code is executing in a nondefault context, specifying true for exitContext causes the thread to exit the nondefault managed context (that is, to transition to the default context) before executing the SignalAndWait method. The thread returns to the original nondefault context after the call to the SignalAndWait method completes.
This can be useful when the context-bound class has SynchronizationAttribute. In that case, all calls to members of the class are automatically synchronized, and the synchronization domain is the entire body of code for the class. If code in the call stack of a member calls the SignalAndWait method and specifies true for exitContext, the thread exits the synchronization domain, allowing a thread that is blocked on a call to any member of the object to proceed. When the SignalAndWait method returns, the thread that made the call must wait to reenter the synchronization domain.
Windows 98, Windows Server 2000 SP4, Windows Millennium Edition, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter EditionThe Microsoft .NET Framework 3.0 is supported on Windows Vista, Microsoft Windows XP SP2, and Windows Server 2003 SP1.