The SocketTools File Transfer .NET component enables you to quickly and easily incorporate file transfer functionality in your applications, using either the File Transfer Protocol (FTP) or Hypertext Transfer Protocol (HTTP). In addition to uploading and downloading files, the class also supports remote file management functionality such as directory listings and the ability to rename, delete and move files on the server. The File Transfer .NET component provides a high-level interface, and does not require that you understand network programming or how the specific application protocols work. In most cases, only a few lines of code are required to implement a file transfer in your application.
One of the advantages of the File Transfer component is that it provides a single, unified interface for sending and receiving files using both the FTP and HTTP protocols. For most applications, this is the only component that you'll need to implement complete file transfer functionality in your software. However, in some cases your application may require some of the advanced features SocketTools product. In this situation, the File Transfer class can be seamlessly integrated with the other SocketTools .NET components to build a more complex solution that requires a greater degree of customization.
In addition to supporting standard FTP and HTTP sessions, the File Transfer .NET class also supports secure SSL and TLS connections. By simply setting a few properties, a secure connection using up to 256-bit encryption can be established, providing your application with the greatest flexibility and highest level of security available. Even advanced options such as client certificates are seamlessly supported.
For developers who have used the ActiveX version of the File Transfer control, you'll immediately find yourself in familiar territory. The File Transfer .NET class interface has properties, methods and events that are very similar to the control that you've used in languages like Visual Basic 6.0. It is important to keep in mind that File Transfer .NET is a managed code class, not a wrapper around the ActiveX control, so there will be some inherent differences. However, whenever possible the class interface was designed to make the transition from the ActiveX control as easy as possible.
Comments