VB.NET TCP Client - Server Socket Communications Often we need to use TCP over IP sockets to do communications instead of the familiar HTTP protocol that web developers are used to. Prior to the arrival of the .NET platform, this usually involved a ton of Winsock code and C - style API declarations. I recently had to rewrite a TCP socket client class from VB 6.0 into .NET for communication to a mainframe system
	How to spread tcplistener incoming connections over threads in .NET? The idea is to start a new thread when a new incoming connection is accepted, while the tcplistener then stays available for further incoming connections (and for every new incoming connection a new thread is created). All communication and termination with the client that originated the connection will be handled in the thread.
	Mike Woodring's .NET Sample Page This page contains sample code I've written to demonstrate various things on the .NET platform. If you have specific questions about any of these samples, you can email me at mike@bearcanyon.com. If you have general questions about .NET that aren't specifically about the code in my samples, please do not email me. Instead, search the archives of DevelopMentor's public mailing lists. Most of the topics on this page are discussed on the DOTNET-CLR list. And because numerous very sharp people participate on this list, you're more likely to get a quick response to your question. Please just be sure to check the archives first to avoid posting something that's been asked and answered already.
	.NET Remoting with an easy example .NET Remoting is a mechanism for communicating between objects which are not in the same process. It is a generic system for different applications to communicate with one another. .NET objects are exposed to remote processes, thus allowing inter process communication. The applications can be located on the same computer, different computers on the same network, or on computers across separate networks. Microsoft .NET Remoting provides a framework that allows objects to interact with each other across application domains. Remoting was designed in such a way that it hides the most difficult aspects like managing connections, marshaling data, and reading and writing XML and SOAP. The framework provides a number of services, including object activation and object lifetime support, as well as communication channels which are responsible for transporting messages to and from remote applications.