| A POP3 Client and C# |
| C#Today |
| In this article, Levent Camlibel looks at how to create a POP3 client that recieves e-mail from a POP3 server, showing how the .NET platform allows this project to be created in a very short space of time. Over the course of the article, he looks at POP3 standards, .NET network programming, and custom POP3 objects. |
|
| Create a DotNet TCP/IP Client Class Using Asynchronous Delegates |
| STANDARDIO.ORG |
| In this article, I will demonstrate how manage a DotNet client connection to a TCPIP address and port. All of the necessary components are located under the System.Net.Sockets namespace. We will use the TCPClient and NetworkStream classes to accomplish the task. |
|
| Creating a Multi-User TCP Chat Application |
| MSDN |
| The .NET support for socket-based programming within Visual Basic is dramatically improved over what we had in Visual Basic 6. So even though we approach the programming issue somewhat differently, it is worth it due to all the new capabilities at our disposal. |
|
| Distributing Objects in Visual Basic .NET |
| MSDN |
| The challenge we have faced in the past is that it isn't always easy to give a developer an object, especially across the network. Objects in COM are always passed by reference, meaning that the COM object remains in the process and on the machine where it was created. The client code merely gets a reference to the object, so each method call is marshaled across the network, back to the original object to be serviced. With Microsoft .NET, we have the option of passing our objects either by reference like COM, or by value. When an object is passed by value, we not only get a copy of the data, but we get an actual instance of the object on our client workstation. The object itself physically moves from the server machine to our client machine, meaning that our client application not only has the data we need, but we have the business logic relating to that data as well. |
|
| Dr. GUI.NET #7 |
| MSDN |
| In this article Dr GUI discusses how file and console I/O is achieved in .NET. The article includes a detailed discussion on streams. |
|
| Email Notifier |
| C# Corner |
| Email notifier is TCP/IP application that notifies the user if there is email in the user's email server. This application checks email in default time interval of 5 minutes. You can change it with configure menu. This application is a tray application. |
|
| Peer-to-Peer |
| C# Help |
| The P2P concept generally consists of a central Index server. This server does not contain any files, physically. It only maintains the information about the users who are logged on to the network, the IP address of the client and the list of files shared at any given moment by a user. The client and the server communicate with each other over a socket connection using simple commands. |
|
| Picture Chat using C# |
| The Code Project |
| Chat program that support unicode inputs and picture transfer |
|
| POP3 Client as a C# Class |
| The Code Project |
| After reading Agus Kurniawan's article on using C# to communicate with a POP3 server I decided that I'd get a lot more milage if I built up a class that would act as a POP3 client. I decided to implement methods for each of the standard POP3 commands, with each method returning a string containing the response of the POP3 server (where appropriate.) In some situations the command is not valid so the methods detect this and returns an error message rather then sending the command to the server. The source code accompanying this article contains the class definitions and the demo console application (shown above) shows how to use the class to retrieve from a POP3 mail server. |
|
| Read POP3 Email with ASP.NET |
| ASP Alliance |
| Just recently I was sent an email with attachments totalling 28mb to my home dialup email account. While I was telnetting into my account to delete the offending email I was inspired to write this article showing how you might do the same thing in code! |
|
| Run-time Serialization |
| MSDN |
| In this three-part series of columns, I will explain how the .NET Framework exposes its serialization and deserialization services. For almost all data types, the default behavior of these services will be sufficient, meaning that it takes almost no work for you to make your own types serializable. However, there is a small minority of types for which the serialization service's default behavior will not be sufficient. Fortunately, the serialization services are very extensible, and I will explain in these three columns how to tap this extensibility to do some pretty powerful things when serializing or deserializing objects. |
|
| SMTP Email Client |
| C# Help |
| This is a web
based smtp email program. This program can be used to send a email
through a SMTP server. User can specify SMTP server IP, sender's mail
address, recipient's email address and mail content. When the user
clicks on "send mail" button , mail is forwarded to SMTP
server which in turn forwards the mail to recepient. |
|
| Synchronize access to stream data section by section |
| The Code Project |
| An article about locking sections of a stream for reading and writing. |
|
| TabletPC 1.0 Advanced Remote Control |
| The Code Project |
| TabletPC turns your PocketPC into a tablet input device for your workstation or laptop. It can be used as a mouse or a keyboard. It has a friendly intuitive interface. |
|
| TCP Date Time Client/Server |
| Master C# |
| This is the implementation of "System.Net.Sockets". In this example we will learn how to use the "TCPListener" and "TCPClient" classes from the "System.Net.Sockets" namespace. |
|
| Utilize the full functionality of Whidbey File Management from VB.NET |
| The Code Project |
| Article on Whidbey File Management |
|
| VB.NET TCP Client - Server Socket Communications |
| Egg Head Cafe |
| Here's a sample TCP Client and associated server "listener" to illustrate how easy socket programming has become in .NET. I'm keeping this synchronous and very basic; the idea is you have a client that accepts an input message, makes a connection to the listener on a specific address and port, sends the message, and retrieves the response. The sockets are then closed. These are console apps so you can easily see what's going back and forth, but it is trivial to compile the client code into a class library to allow multithreaded socket messaging even from ASPX pages, assuming that a listener exists that is equipped to handle the incoming requests correctly without serializing them. |
|
