Socket.BeginSendFile Method (String, Byte(), Byte(), TransmitFileOptions, AsyncCallback, Object)
Sends a file and buffers of data asynchronously to a connected Socket object.
Assembly: System (in System.dll)
<HostProtectionAttribute(SecurityAction.LinkDemand, ExternalThreading := True)> Public Function BeginSendFile ( fileName As String, preBuffer As Byte(), postBuffer As Byte(), flags As TransmitFileOptions, callback As AsyncCallback, state As Object ) As IAsyncResult
A string that contains the path and name of the file to be sent. This parameter can be null.
A Byte array that contains data to be sent before the file is sent. This parameter can be null.
A Byte array that contains data to be sent after the file is sent. This parameter can be null.
A bitwise combination of TransmitFileOptions values.
An AsyncCallback delegate to be invoked when this operation completes. This parameter can be null.
A user-defined object that contains state information for this request. This parameter can be null.
The Socket object has been closed.
An error occurred when attempting to access the socket. See remarks section below.
The operating system is not Windows NT or later.
- or -
The socket is not connected to a remote host.
The file fileName was not found.
This overload requires the name of the file you want to send and a bitwise combination of TransmitFileOptions values. The preBuffer parameter contains any data you want to precede the file. postBuffer contains data you want to follow the file. If fileName is in the local directory, it may be identified with just the name of the file; otherwise, the full path and name of the file must be specified. Wildcards ("..\\myfile.txt") and UNC share names ("\\\\shared directory\\myfile.txt") are supported. If the file is not found, the exception FileNotFoundException is thrown.
The flags parameter provides the Window Sockets service provider with additional information about the file transfer. For more information about how to use this parameter, see TransmitFileOptions.
This method uses the TransmitFile function found in the Windows Sockets 2 API. For more information about the TransmitFile function and its flags, see the Windows Sockets documentation in the MSDN Library.
The BeginSendFile method starts an asynchronous send operation to the remote host established in the Connect, BeginConnect, Accept, or BeginAccept methods. BeginSendFile throws an exception if you do not first call Accept, BeginAccept, Connect, or BeginConnect. Calling the BeginSendFile method gives you the ability to send a file within a separate execution thread.
To complete the operation, you can create a callback method that is invoked by the AsyncCallback delegate parameter. To do this, at the very minimum, the state parameter must contain the Socket object being used for communication. If your callback needs more information, you can create a class or structure to hold the Socket and the other required information. Pass an instance of this custom object to theBeginSendFile method through the state parameter.
Your callback method must invoke the EndSendFile method. When your application calls BeginSendFile, the system uses a separate thread to execute the specified callback method, and blocks on EndSendFile until the Socket sends the entire file or throws an exception. For additional information on writing callback methods see Marshaling a Delegate as a Callback Method.
Although intended for connection-oriented protocols, BeginSendFile also works for connectionless protocols, provided that you first call the Connect or BeginConnect method to establish a default remote host. With connectionless protocols, you must also be sure that the size of your file does not exceed the maximum packet size of the underlying service provider. If it does, the datagram is not sent and BeginSendFile throws a SocketException exception.
If you receive a SocketException exception, 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 in the .NET Framework.
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.
The following code example creates and connects a socket for asynchronous communication and begins sending the file "text.txt" asynchronously to the remote host. In this example, a preBuffer and a postBuffer of data is created to send with the file and the default TransmitFileOptions value is used. The callback delegate calls EndSendFile to complete the transmission.
Available since 2.0