When using a connection-oriented System.Net.Sockets.Socket, always call the Socket.Shutdown(SocketShutdown) method before closing the System.Net.Sockets.Socket. This ensures that all data is sent and received on the connected socket before it is closed.

Call the Socket.Close method to free all managed and unmanaged resources associated with the System.Net.Sockets.Socket. Do not attempt to reuse the System.Net.Sockets.Socket after closing.

The following table shows the System.Net.Sockets.SocketShutdown enumeration values that are valid for the how parameter.

Send	Disable sending on this System.Net.Sockets.Socket.
Receive	Disable receiving on this System.Net.Sockets.Socket.
Both	Disable both sending and receiving on this System.Net.Sockets.Socket.

Setting how to SocketShutdown.Send specifies that subsequent calls to Socket.Send(Byte[], int, SocketFlags) are not allowed. If you are using a connectionless System.Net.Sockets.Socket, specifying SocketShutdown.Send will have no effect.

Setting how to SocketShutdown.Receive specifies that subsequent calls to Socket.Receive(Byte[], int, SocketFlags) are not allowed. This has no effect on lower protocol layers. If you are using a connection-oriented protocol, the connection is terminated if either of the following conditions exist after a call to Socket.Shutdown(SocketShutdown) :

• Data is in the incoming network buffer waiting to be received.

• More data has arrived.

If you are using a connectionless protocol, datagrams are accepted and queued. However, if no buffer space is available for additional incoming datagrams, they will be discarded and no error will be returned to the sender. Using Socket.Shutdown(SocketShutdown) on a connectionless System.Net.Sockets.Socket is not recommended.

Setting how to SocketShutdown.Both disables both sends and receives as described above.

Namespace: System.Net.Sockets
Assembly: System (in System.dll)
Assembly Versions: 1.0.5000.0, 2.0.0.0, 4.0.0.0