Back to product page
- Introduction
- Overview
- License agreement
- Getting Started
- Objects
- Enumerations
- wodSFTP
- Methods
- Abort
- About
- AppendData
- AppendFile
- Connect
- DeleteFile
- DeleteFiles
- Disconnect
- ExtendedCmd
- GetAttributes
- GetData
- GetDataAt
- GetFile
- GetFileAt
- GetFiles
- ListAttributes
- ListDir
- ListNames
- LoopFiles
- MakeDir
- PutData
- PutDataAt
- PutFile
- PutFileAt
- PutFiles
- RealPath
- RemoteClose
- RemoteOpen
- RemoteRead
- RemoteWrite
- RemoveDir
- Rename
- SetAttributes
- SetAttributes64
- Properties
- Authentication
- Blocking
- BufferSize
- ClientName
- Compression
- Encryption
- EncryptionList
- ErrorText
- Extensions
- FingerPrint
- FIPS
- HMacList
- Hostname
- KeepAlives
- KeyExchangeList
- KeySignatureList
- LastError
- ListItem
- LocalPath
- Login
- MaxTransferRate
- MyHostname
- MyIP
- Notification
- Password
- Port
- PrivateKey
- ProxyHostname
- ProxyLogin
- ProxyPassword
- ProxyPort
- ProxyType
- RemoteIdentification
- RemotePath
- Resume
- ServerErrorCode
- ServerErrorText
- State
- StateText
- Timeout
- Timezone
- TransferMode
- TransferRate
- TransferTime
- UseIPv6
- Version
- Events
- Methods
- IwodSFTPNotify
- SftpItem
- SftpItems
- How to get support?
- Technical information
- Fast notifications interface
- Error list
Technical and distribution information
General
The wodSFTP component has two versions (both included in the package):wodSFTPCom is a COM object (wodSFTP.dll) that is designed to be initialized dynamically from your code and declared from within your code. It does not have a user interface - it is windowless. Usually, you will initialize it with:
Dim WithEvents Sftp1 as wodSFTPCom
and wodSFTP is an ActiveX control (wodSFTP.ocx) that is designed to be put on your application's forms using drag & drop from the control toolbox. Once you put it onto a form, no special code is required to initialize it as your environment (usually VB) will handle this.
Unlike ActiveX controls which are licensed the moment you put them on the form (if you have a licensed version of wodSFTP), COM object licensing is not directly supported by any container. Therefore you need to add an extra line to your code in order to correctly license wodSFTP:
Sftp1.LicenseKey = "put.your.key.here"
COM Object information | |
---|---|
Filename | wodSFTP.DLL (wodSFTP64.DLL for x64) |
Class name | WeOnlyDo.wodSFTPCom.1 |
Class ID | {79731811-6B9A-4DF0-92CF-991C37D2BCED} |
Events class ID | {0xEAF8E315,0x3A6C,0x485B,{0xA1,0x28,0x4B,0x87,0x10,0x81,0x59,0x9C}} |
Compatibility | VB 5.0 and above, VFP 5.0 and above |
Built with | Microsoft Visual Studio 2008 C++, OpenSSL |
Required DLLs | None required, wodKeys.dll optional, only if Key generation/loading/saving is used. |
ActiveX Control information | |
---|---|
Filename | wodSFTP.OCX (wodSFTP64.OCX for x64) |
Class name | WeOnlyDo.wodSFTP.1 |
Class ID | {6795FA0F-35C3-4BEB-B3AA-F19DB0B228EA} |
Events class ID | {0x1CCB7958,0x5EDE,0x4EA1,{0xA7,0xAE,0x3A,0x8D,0xBE,0x50,0x4B,0x63}} |
Compatibility | VB 5.0 and above, VFP 5.0 and above |
Built with | Microsoft Visual Studio 2008 C++, OpenSSL |
Required DLLs | None required, wodKeys.dll optional, only if private keys are used. |
Interfaces | |
---|---|
ISftpItem | {B42C482D-FE98-415C-BA8C-725DB78C38CD} |
ISftpItems | {84F0870F-25B0-492A-9FB1-05432227F6D4} |
IwodSFTPNotify | {98C7F28F-FE9C-4540-9AAB-2B43EDD6328F} |
Documentation | |
---|---|
Help filename | wodSFTP.CHM |
Distribution note
When you develop and distribute an application that uses this component:- Choose whether to include the COM object (wodSFTP.DLL/wodSFTP64.DLL) or the ActiveX control (wodSFTP.OCX/wodSFTP64.OCX) into the installation package. The COM object and the ActiveX control are independent of each other.
- You should include wodKeys.DLL/wodKeys64.DLL for Key management if it is needed in your application. wodSFTP does not depend on it, it only uses it for client authentication with the private key.
- The above binaries can be included royalty-free in your application.
- Use RegSvr32.EXE (or any other installation package creator) to register both the OCX and the DLL. Usually the installation software will do this for you.
- Install the component file(s) into the user's Windows SYSTEM32 folder. The component files have version information built into them, so during installation you should ensure that you are not overwriting a newer version.