Begins to asynchronously receive the specified number of bytes of data into the specified location of the data buffer, using the specified SocketFlags, and stores the endpoint and packet information..
Assembly: System (in System.dll)
member BeginReceiveMessageFrom : buffer:byte * offset:int * size:int * socketFlags:SocketFlags * remoteEP:EndPoint byref * callback:AsyncCallback * state:Object -> IAsyncResult
- Type: System.Int32
The zero-based position in the buffer parameter at which to store the data.
- Type: System.Int32
The number of bytes to receive.
- Type: System.Object
An object that contains state information for this request.
buffer is a null reference (Nothing in Visual Basic).
remoteEP is a null reference (Nothing in Visual Basic).
An error occurred when attempting to access the socket. See the Remarks section for more information.
offset is less than 0.
offset is greater than the length of buffer.
size is less than 0.
size is greater than the length of buffer minus the value of the offset parameter.
The Socket has been closed.
The operating system is Windows 2000 or earlier, and this method requires Windows XP.
The asynchronous receive operation must be completed by calling the EndReceiveMessageFrom method. Typically, the method is invoked by the asyncCallback delegate.
This method does not block until the operation completes. To block until the operation completes, use the ReceiveMessageFrom method.
To cancel a pending , call the Close method.
For detailed information about using the asynchronous programming model, see Calling Synchronous Methods Asynchronously
This method reads data into the buffer parameter, and captures the remote host endpoint from which the data is sent, as well as information about the received packet. For information on how to retrieve this endpoint, refer to EndReceiveFrom. This method is most useful if you intend to asynchronously receive connectionless datagrams from an unknown host or multiple hosts.
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.
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 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.