Associates a socket with a specific local endpoint. You do not need to call Bind before using the ConnectAsync method unless you need to use a specific local endpoint.
Assembly: System.Net (in System.Net.dll)
localEP is null.
An error occurred when attempting to access the socket. If you receive a SocketException, use the SocketException.ErrorCode property to obtain the specific error code.
The Socket has been closed.
A caller higher in the call stack does not have permission for the requested operation.
Use the Bind method if you need to use a specific local endpoint. You must call Bind before you can call the Listen method. You do not need to call Bind before using the ConnectAsync method unless you need to use a specific local endpoint. You can use the Bind method on both connectionless and connection-oriented protocols.
If you use the above approach, you can discover what local network address and port number has been assigned by calling the LocalEndPoint. If you are using a connection-oriented protocol, LocalEndPoint will not return the locally assigned network address until after you have made a call to the ConnectAsync method. If you are using a connectionless protocol, you will not have access to this information until you have completed a send or receive.
Before calling Bind, you must first create the local IPEndPoint from which you intend to communicate data. If you do not care which local address is assigned, you can create an IPEndPoint using Any as the address parameter, and the underlying service provider will assign the most appropriate network address. This might help simplify your application if you have multiple network interfaces. If you do not care which local port is used, you can create an IPEndPoint using 0 for the port number. In this case, the service provider will assign an available port number between 1024 and 5000.
If you intend to receive multicast datagrams, you must call the Bind method with a multicast port number.