.NET lacks FTP classes. KCommon FTP component lets programmers build .NET apps so users can send or receive files via FTP. Supports synchronous and asynchronous transfers. Supports passive but not active mode. Written in C#. Doesnâ€™t support proxies.
Version: 1.0Microsoftâ€™s .NET Framework class library contains no classes that will allow developers to access File Transfer Protocol (FTP) services directly. KCommonâ€™s FTP component was designed to compensate for the fact that .NET lacks FTP support.
Operating System: Windows
With this FTP component, programmers can build either Windows Forms or ASP.NET (Web Forms) applications that will allow users to send or receive a single file or multiple files, using the FTP protocol. Operations for synchronous and asynchronous (using a callback or an event) transfers are supported. KCommon supports passive mode, but does not support active mode, which could cause problems with poorly written firewalls.
Recall that in passive mode, the data flow is set up and initiated by the FTP client, rather than the server. This means improved security for the client computer, because it wonâ€™t have to deal with data flow being set up by the server.
The component is written in C#. It is not marked as CLS compliant. It does not support proxy servers. The online description erroneously refers to an FtpSession type (it should be Session).