Network Programming in C#: From Sockets to Web API

Diving into Network Depths: Why C# is the Ideal Choice

When we talk about network programming, many developers imagine tons of low-level C code or endless Python configs. But C# with its elegant syntax and powerful standard library turns communication between applications into a real pleasure. Forget boring manuals — today we'll break down how to create a full-fledged TCP chat, an asynchronous client-server, and even a REST API using only the built-in tools of .NET.

At pythonlib.ru we are used to Python, but C# in the field of network interactions gives a head start to many languages. Its asynchronous model (async/await) and built-in socket support allow you to write code that easily scales from a simple console application to a high-load server. Ready? Then let's launch Visual Studio and get started!

Basics: What is a Socket and How to Prepare It

A socket is a software interface for exchanging data between processes that can be on the same machine or on opposite sides of the world. In C#, working with sockets begins with the namespace System.Net.Sockets. The most popular pair is TCP sockets, which provide reliable data delivery.

Imagine that a socket is a door. One side (the server) opens the door and waits for someone to knock. The other side (the client) knocks, and after a handshake, they start exchanging messages. In C#, it looks like this:

// Server side\nusing System.Net;\nusing System.Net.Sockets;\nusing System.Text;\n\nTcpListener server = new TcpListener(IPAddress.Any, 8888);\nserver.Start();\nConsole.WriteLine("Server started, waiting for connections...");\n\nTcpClient client = await server.AcceptTcpClientAsync();\nNetworkStream stream = client.GetStream();\n\nbyte[] buffer = new byte[1024];\nint bytesRead = await stream.ReadAsync(buffer, 0, buffer.Length);\nstring message = Encoding.UTF8.GetString(buffer, 0, bytesRead);\nConsole.WriteLine($"Received: {message}");\n\n// Reply to client\nbyte[] response = Encoding.UTF8.GetBytes("Hello from server!");\nawait stream.WriteAsync(response, 0, response.Length);

This code is the foundation. It is synchronous, but already gives an idea of how network programming in C# works. Notice that we use async and await — this is the key to performance.

Client-Server Communication: First Contact

The client side is no less simple. Here is an example of a TCP client that connects to our server:

// Client\nTcpClient client = new TcpClient();\nawait client.ConnectAsync("127.0.0.1", 8888);\nNetworkStream stream = client.GetStream();\n\nbyte[] data = Encoding.UTF8.GetBytes("Hello everyone!");\nawait stream.WriteAsync(data, 0, data.Length);\n\nbyte[] buffer = new byte[1024];\nint bytesRead = await stream.ReadAsync(buffer, 0, buffer.Length);\nConsole.WriteLine($"Response: {Encoding.UTF8.GetString(buffer, 0, bytesRead)}");

\n
• IPAddress.Any — listen on all network interfaces.
\n
• Port 8888 — any free port above 1024.
\n
• NetworkStream — stream for reading/writing.
\n

Important nuance: don't forget to close connections. In real projects, use using or try-finally.

Asynchronous Programming: How Not to Hang the Server

Synchronous code is good for learning, but in production it will block the thread while waiting. Imagine that 100 clients connect to your server — each one will wait in line. The solution is asynchronous network programming in C#.

Methods with the Async suffix (e.g., AcceptTcpClientAsync) do not block the thread. They return control immediately, and when data arrives, they resume execution. This allows you to handle