MessageQueue.BeginPeek Method (TimeSpan, Cursor, PeekAction, Object, AsyncCallback)


Initiates an asynchronous peek operation that has a specified time-out and that uses a specified cursor, a specified peek action, and a specified state object. The state object provides associated information throughout the lifetime of the operation. This overload receives notification, through a callback, of the identity of the event handler for the operation. The operation is not complete until either a message becomes available in the queue or the time-out occurs.

Namespace:   System.Messaging
Assembly:  System.Messaging (in System.Messaging.dll)

public IAsyncResult BeginPeek(
	TimeSpan timeout,
	Cursor cursor,
	PeekAction action,
	object state,
	AsyncCallback callback


Type: System.TimeSpan

A TimeSpan that indicates the interval of time to wait for a message to become available.

Type: System.Messaging.Cursor

A Cursor that maintains a specific position in the message queue.

Type: System.Messaging.PeekAction

One of the PeekAction values. Indicates whether to peek at the current message in the queue, or the next message.

Type: System.Object

A state object, specified by the application, that contains information associated with the asynchronous operation.

Type: System.AsyncCallback

The AsyncCallback that receives the notification of the asynchronous operation completion.

Return Value

Type: System.IAsyncResult

The IAsyncResult that identifies the posted asynchronous request.

Exception Condition

A value other than PeekAction.Current or PeekAction.Next was specified for the action parameter.


The cursor parameter is null.


The value specified for the timeout parameter is not valid.


An error occurred when accessing a Message Queuing method.

.NET Framework
Available since 2.0

The method is not thread safe.

When you use this overload, the callback specified in the callback parameter is invoked directly when a message becomes available in the queue or when the specified interval of time has expired. The PeekCompleted event is not raised. The other overloads of BeginPeek rely on this component to raise the PeekCompleted event.

PeekCompleted is also raised if a message already exists in the queue.

The BeginPeek method returns immediately, but the asynchronous operation is not completed until the event handler is called.

Because BeginPeek is asynchronous, you can call it to peek the queue without blocking the current thread of execution. To synchronously peek the queue, use the Peek method.

Once an asynchronous operation completes, you can call BeginPeek or BeginReceive again in the event handler to keep receiving notifications.

BeginPeek returns a IAsyncResult that identifies the asynchronous operation started by the method. You can use this IAsyncResult throughout the lifetime of the operation, although you generally do not use it until EndPeek(IAsyncResult) is called. However, if you start several asynchronous operations, you can place their IAsyncResult values in an array and specify whether to wait for all operations or any operation to complete. In this case, use the AsyncWaitHandle property of the IAsyncResult to identify the completed operation.

The state object associates state information with the operation. For example, if you call BeginPeek multiple times to initiate multiple operations, you can identify each operation through a separate state object that you define.

The following table shows whether this method is available in various Workgroup modes.

Workgroup mode


Local computer


Local computer and direct format name


Remote computer


Remote computer and direct format name


Return to top