.NET technology

• Works with .NET Compact Framework 2.0 and up.
• 100% managed code written in C# (source code included in the Blueprint Edition).
• Superior object-oriented design.
• Seamless integration with the .NET base class libraries, with error handling exclusively through .NET exception classes.
• Objects don't need to be explicitly disposed of.
• CLS compliant (Common Language Specification) with no unsafe blocks, for minimal permission requirements.
• Documentation fully integrated into Visual Studio.

FTP protocol features

• RFC 959, 1123, and 1579 compliant.
• Supports the FEAT command, also known as "Knowledge of Extra Capabilities".
• Supports for MODE Z data transfer.
• Enables connections to FTP servers through HTTP proxy servers.
• Solid, built-in support for various server types including Unix, VMS, AS/400, and DOS.
• Supports all major FTP operations and allows sending of custom commands.
• Supports FTP passive mode for firewall and proxy server resilience.

Multi-talented capabilities

• Abstracts files and folders on FTP sites and locally, in streams and in memory, so you can write your code as if you are manipulating regular files or folders on a local disk. When support is added for more archive types and locations, there's no need to change your code in order to work with the new file and folder types or locations.

Major features

• Exposes Xceed's unique, flexible FileSystem object model for deep integration with Xceed Zip for .NET. Lets you work with files and folders on an FTP server as if they were local. See this blog post for details.
• Send and receive files, folders, or entire directory structures quickly and easily.
• Send and receive files to or from disk or memory streams.
• Synchronise a local directory structure with a remote directory structure on an FTP server and vice-versa.
• Support for non-blocking (asynchronous) FTP operations.
• Operations can be aborted at any time.
• Provides a rich set of events to keep your application notified of all FTP activity.
• Allows you to verify at any time the exact state of the component, including whether it is connected or not, busy or not, sending, receiving, deleting, etc.
• Obtain a detailed listing of files on the FTP server via a collection object or by events.
• Rename and delete files on the FTP server.
• Resume file transfers from any byte offset.

Component interactivity / Events

• Provides status report events on a file-by-file basis, as well as on the entire operation being performed.
• Status reports include various completion percentages, byte counts, file counts, bytes per second, bytes skipped, number of files skipped, and more. Displaying a progress bar could not be easier.
• Events are triggered for all major operations, such as whenever a file is being sent, received, listed, etc.
• When sending multiple files and an error occurs, allows you to retry the file, skip it and continue, or abort the entire operation.
• Provides complete file information for the current file being processed.

Other features

• Create filters so you can send or receive only files that fit specific criteria, such as file size or date.
• Allows you to rename or change filenames and paths before sending.
• Automatic logging to memory or to disk.
• Use the automatic directory listing parser or create your own custom parser for unknown listing formats and FTP server types. You can do this in two ways: through inheritance or by handling an event.
• Set a timeout limit on all operations and have an exception triggered if it is exceeded.
• Send a file to an FTP server and have the server give it a unique filename.
• Send files as ASCII or Binary.
• Triggers an event if the connection to the FTP server is lost.
• Allows you to change the user that is currently logged in without disconnecting.
• Built-in tweaks for working with non-standard FTP server types including settable FTP server folder separator character, storage pre-allocation and TYPE command sending.
• Specify an FTP server by IP address or host name.
• Specify files to send or receive using wildcards.

.NET technology

• Works with .NET Compact Framework 2.0 and up.
• 100% managed code written in C# (source code included in the Blueprint Edition).
• Superior object-oriented design.
• Seamless integration with the .NET base class libraries, with error handling exclusively through .NET exception classes.
• Objects don't need to be explicitly disposed of.
• CLS compliant (Common Language Specification) with no unsafe blocks, for minimal permission requirements.
• Documentation fully integrated into Visual Studio.

FTP protocol features

• RFC 959, 1123, and 1579 compliant.
• Supports the FEAT command, also known as "Knowledge of Extra Capabilities".
• Supports for MODE Z data transfer.
• Enables connections to FTP servers through HTTP proxy servers.
• Solid, built-in support for various server types including Unix, VMS, AS/400, and DOS.
• Supports all major FTP operations and allows sending of custom commands.
• Supports FTP passive mode for firewall and proxy server resilience.

Multi-talented capabilities

• Abstracts files and folders on FTP sites and locally, in streams and in memory, so you can write your code as if you are manipulating regular files or folders on a local disk. When support is added for more archive types and locations, there's no need to change your code in order to work with the new file and folder types or locations.

Major features

• Exposes Xceed's unique, flexible FileSystem object model for deep integration with Xceed Zip for .NET. Lets you work with files and folders on an FTP server as if they were local. See this blog post for details.
• Send and receive files, folders, or entire directory structures quickly and easily.
• Send and receive files to or from disk or memory streams.
• Synchronise a local directory structure with a remote directory structure on an FTP server and vice-versa.
• Support for non-blocking (asynchronous) FTP operations.
• Operations can be aborted at any time.
• Provides a rich set of events to keep your application notified of all FTP activity.
• Allows you to verify at any time the exact state of the component, including whether it is connected or not, busy or not, sending, receiving, deleting, etc.
• Obtain a detailed listing of files on the FTP server via a collection object or by events.
• Rename and delete files on the FTP server.
• Resume file transfers from any byte offset.

Component interactivity / Events

• Provides status report events on a file-by-file basis, as well as on the entire operation being performed.
• Status reports include various completion percentages, byte counts, file counts, bytes per second, bytes skipped, number of files skipped, and more. Displaying a progress bar could not be easier.
• Events are triggered for all major operations, such as whenever a file is being sent, received, listed, etc.
• When sending multiple files and an error occurs, allows you to retry the file, skip it and continue, or abort the entire operation.
• Provides complete file information for the current file being processed.

Other features

• Create filters so you can send or receive only files that fit specific criteria, such as file size or date.
• Allows you to rename or change filenames and paths before sending.
• Automatic logging to memory or to disk.
• Use the automatic directory listing parser or create your own custom parser for unknown listing formats and FTP server types. You can do this in two ways: through inheritance or by handling an event.
• Set a timeout limit on all operations and have an exception triggered if it is exceeded.
• Send a file to an FTP server and have the server give it a unique filename.
• Send files as ASCII or Binary.
• Triggers an event if the connection to the FTP server is lost.
• Allows you to change the user that is currently logged in without disconnecting.
• Built-in tweaks for working with non-standard FTP server types including settable FTP server folder separator character, storage pre-allocation and TYPE command sending.
• Specify an FTP server by IP address or host name.
• Specify files to send or receive using wildcards.