Technical information

wodTelnetDLX component has two versions (both included in the package):

wodTelnetDLXCom is a COM object (wodTelnetDLX.dll), designed to be initialized dynamically from your code, and declared from within your code. It does not have user interface, it is windowless. Usually, you will initialize it with

and wodTelnetDLX as ActiveX control (wodTelnetDLX.ocx) - designed to be put on application's form using drag&drop from control toolbox. Once you put it on the form, no special code is required to initialize it, since your environment (usually VB) will handle it. It has it's own explorer-alike user interface.

COM object licensing is not directly supported by any container. Unlike ActiveX controls which are licensed the moment you put them on the form (if you have licensed version of wodTelnetDLX, of course), you need one more line to put in your code to license wodTelnetDLX correctly:

COM Object information
Filename	wodTelnetDLX.DLL (wodTelnetDLX64.DLL for x64)
Class name	WeOnlyDo.wodTelnetDLXCom.1
Class ID	{675776B1-0DA1-4390-A291-5485076F0763}
Events class ID	{0x4CDF4AF3,0x7621,0x4698,{0x88,0xE1,0xA7,0x57,0x73,0x2A,0xB6,0x5A}}
Compatibility	VB 5.0 and above, VFP 5.0 and above
Built with	Microsoft Visual Studio 2008 C++, OpenSSL
Required DLLs	None required, wodCertificate.dll optional, only if certificates are used.

ActiveX Control information
Filename	wodTelnetDLX.OCX (wodTelnetDLX64.OCX for x64)
Class name	WeOnlyDo.wodTelnetDLX.1
Class ID	{B7039D87-D648-4431-BA87-C3A04E6111DA}
Events class ID	{0x5890091F,0x6364,0x46D1,{0xB3,0xAF,0x16,0xB7,0x50,0x14,0x2B,0xD1}}
Compatibility	VB 5.0 and above, VFP 5.0 and above
Built with	Microsoft Visual Studio 2008 C++, OpenSSL
Required DLLs	None required, wodCertificate.dll optional, only if certificates are used.

Interfaces
IwodTelnetNotify	{8E663F82-15CB-4d49-B532-469C3E75794E}

Documentation
Help filename	wodTelnetDLX.CHM

Distribution note

When you develop and distribute an application that uses this component:

1. Choose between COM object (wodTelnetDLX.DLL/wodTelnetDLX64.DLL) and the ActiveX control (wodTelnetDLX.OCX/wodTelnetDLX64.DLL) to include into the installation package. Both versions are independent on each other.

2. You should include wodCertificate.DLL/wodCertificate64.DLL for Certificate management - if it is needed in your application. wodTelnetDLX does not depend on it - only uses it for client authentication with the certificate or private key.

3. Above binaries can be included royalty-free in your application.

4. Use RegSvr32.EXE (or any other installer package creator) to register both the OCX and the DLL. Usually, installer software will do this for you

5. Install the component file(s) into the user's Windows SYSTEM32 folder. The component file(s) has/have version information built into it. So, during installation, you should ensure that you are not overwriting a newer version.

Using licensed version

To use retail (licensed) version in your code, put your license key into LicenseKey property, immediately after initializing the component. For ActiveX control, you cannot do this (there is no LicenseKey property) because your license key will be read internally by wodTelnetDLX.

Platforms

Windows