Socket.BeginReceive Method (Generic IList, SocketFlags, SocketError, AsyncCallback, Object)
Assembly: System (in system.dll)
public IAsyncResult BeginReceive ( IList<ArraySegment<byte>> buffers, SocketFlags socketFlags, out SocketError errorCode, AsyncCallback callback, Object state )
public IAsyncResult BeginReceive ( IList<ArraySegment<byte>> buffers, SocketFlags socketFlags, /** @attribute OutAttribute() */ /** @ref */ SocketError errorCode, AsyncCallback callback, Object state )
An array of type Byte that is the storage location for the received data.
A bitwise combination of the SocketFlags values.
A SocketError object that stores the socket error.
An AsyncCallback delegate that references the method to invoke when the operation is complete.
A user-defined object that contains information about the receive operation. This object is passed to the EndReceive delegate when the operation is complete.
Return ValueAn IAsyncResult that references the asynchronous read.
The asynchronous BeginReceive operation must be completed by calling the EndReceive method. Typically, the method is invoked by the callback delegate.
This method does not block until the operation is complete. To block until the operation is complete, use one of the Receive method overloads.
For detailed information about using the asynchronous programming model, see Calling Synchronous Methods Asynchronously.
If you receive a SocketException, use the SocketException.ErrorCode property to obtain the specific error code. After you have obtained this code, refer to the Windows Sockets version 2 API error code documentation in the MSDN library for a detailed description of the error.
All I/O initiated by a given thread is canceled when that thread exits. A pending asynchronous operation can fail if the thread exits before the operation completes.
state is an instantiation of a user-defined class.
This member outputs trace information when you enable network tracing in your application. For more information, see Network Tracing.
The execution context (the security context, the impersonated user, and the calling context) is cached for the asynchronous Socket methods. After the first use of a particular context (a specific asynchronous Socket method, a specific Socket instance, and a specific callback), subsequent uses of that context will see a performance improvement.
Windows 98, Windows Server 2000 SP4, Windows CE, Windows Millennium Edition, Windows Mobile for Pocket PC, Windows Mobile for Smartphone, 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.