The .NET assembly is still provided for your use, however the team is working
on a full Indy C# port that in the future
will replace this distribution.
Most Indy demos are currently in Delphi (And a few in C++). A few demos have
been uploaded to the Atozed
Indy Portal in C#, Delphi, and Visual Basic. If you are interested in
contributing demos please see the .NET Demo Team
Indy 10 documentation is available in a variety of formats, and can
be downloaded from the Documentation
page. Documentation can also be accessed online in HTML
The existing documentation is geared towards Delphi and examples are written
in Delphi. We are working on updating the documentation to include C# and Visual
Basic examples. Until that time please use the Delphi examples as they easily
translate into C# and Visual Basic. You can also ask questions in the .dotnet
and .visualstudio groups on the Indy
In addition, please check out these articles of special interest to .NET
Indy? - A common question from .net users is: "Why should I use Indy when
.NET has native socket support?". This is a very reasonable question, with
simple but not immediately obvious answers.
for Visual Studio.Net Developers - This article will cover some of the
Indy basics, but is specifically geared towards Visual Studio.NET developers.
It provides source code in C#, Visual Basic, and Delphi. It also answers some
common questions from Visual Studio.NET users.
- Indy in Depth
- The Indy Book by the original Indy author. It cannot get more authoritative
than that! Best of all, its an e-book and you do not have to worry about
shipping as you can download it.
- Table of current VCL to .NET class
names - This will provide you with a translation for both using
documentation, or for users who have used Indy before.
User Contributed Articles
Visual Studio.NET Users
To use Indy in your project, select "Add Reference" from the Project menu.
When the Add Reference dialog appears, click the Browse button and browse to
Indy.Sockets.dll. Now click Open to close the dialog window, and OK to close the
Add Reference window.
Your project is all ready to use Indy. Simply add a using Indy.Sockets (C#)
or Imports Indy.Sockets (VB) to the unit that you wish to use Indy in.
The .NET assembly does not contain all Indy features and protocols yet. We
are adding more and more of them each week. Currently it contains about 95% of
the functionality including TCP clients and servers, UDP, FTP, NNTP, SMTP, POP3,
IMAP4 (client), and more.
- 1.1 .NET Framework
- Visual Studio.NET 2003, or any other .NET Development environment. Visual
Studio.NET 2002 cannot be used because it does not support the 1.1 framework.