MS Docs

Network Sockets API

This document provides an overview of the network sockets API available in the .NET Framework, enabling communication across networks.

Introduction to Sockets

A socket is an endpoint for communication. It's a combination of an IP address and a port number. The Sockets API in .NET provides classes that abstract the underlying operating system's socket implementation, allowing developers to create network applications using familiar object-oriented paradigms.

Core Socket Classes

The primary classes for socket programming in .NET are found within the System.Net.Sockets namespace:

Basic Socket Operations

The Socket class supports both connection-oriented (like TCP) and connectionless (like UDP) communication. Here's a conceptual outline of common operations:

Creating a Socket

You create a socket by specifying the address family (e.g., IPv4 or IPv6), socket type (e.g., Stream for TCP, Dgram for UDP), and protocol (e.g., Tcp or Udp).


using System.Net.Sockets;

// For a TCP/IP socket using IPv4
Socket socket = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp);

Binding and Listening (Server-side)

A server-side socket typically needs to be bound to a local endpoint (IP address and port) and then listen for incoming connections.


using System.Net;

// Assuming 'socket' is already created as above
IPEndPoint localEndPoint = new IPEndPoint(IPAddress.Any, 11000);
socket.Bind(localEndPoint);
socket.Listen(10); // Backlog of 10 pending connections
Console.WriteLine("Server listening on port 11000...");

Connecting (Client-side)

A client socket initiates a connection to a remote endpoint.


using System.Net;

// Assuming 'socket' is already created as above
IPEndPoint remoteEndPoint = new IPEndPoint(IPAddress.Parse("192.168.1.100"), 11000);
socket.Connect(remoteEndPoint);
Console.WriteLine("Connected to server.");

Sending and Receiving Data

Data is sent and received using byte arrays.


// Sending data
byte[] message = System.Text.Encoding.ASCII.GetBytes("Hello, server!");
int bytesSent = socket.Send(message);

// Receiving data
byte[] buffer = new byte[1024];
int bytesReceived = socket.Receive(buffer);
string receivedData = System.Text.Encoding.ASCII.GetString(buffer, 0, bytesReceived);
Console.WriteLine($"Received: {receivedData}");

Closing the Socket

It's crucial to close sockets when they are no longer needed to release resources.


socket.Shutdown(SocketShutdown.Both);
socket.Close();

TCP vs. UDP

Understanding the differences between TCP and UDP is fundamental:

Feature TCP (SocketType.Stream) UDP (SocketType.Dgram)
Connection Connection-oriented Connectionless
Reliability Reliable (guaranteed delivery, order) Unreliable (no guarantees)
Speed Slower (due to handshaking, acknowledgments) Faster (less overhead)
Use Cases Web browsing (HTTP), file transfer (FTP), email (SMTP) Streaming media, online gaming, DNS
Tip: For most common network applications requiring reliable data transfer, TCP is the preferred choice. Use UDP when speed is paramount and occasional data loss is acceptable.

Asynchronous Operations

The Sockets API supports asynchronous operations (e.g., BeginConnect, EndConnect, BeginSend, EndSend) which prevent blocking the calling thread, improving application responsiveness.

Error Handling

Network programming can be prone to errors (e.g., connection refused, network unreachable). Robust applications should include comprehensive error handling using try-catch blocks.

Note: Always ensure that your application properly handles exceptions like SocketException to gracefully manage network failures.

Security Considerations

When dealing with network communication, especially over the internet, security is paramount. Consider implementing encryption (e.g., using SslStream) and validating incoming data to prevent vulnerabilities.

Important: Never trust data received from external sources without proper validation and sanitization.

Further Reading