-
-
General
The wodXMPP component has two versions (both included in
the package):
wodXMPPCom is a COM object (wodXMPP.dll), 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 XMPP1 as wodXMPPCom
and wodXMPP is an ActiveX control (wodXMPP.ocx) -
designed to be put on your application's forms using
drag&drop from the control toolbox. Once you put it on
the form, no special code is required to initialize it, as
your environment (usually VB) will handle it. It has its
own explorer-like user interface.
Unlike ActiveX controls, which are licensed the moment you
put them on the form (if you have a licensed version of
wodXMPP, of course), COM object licensing is not directly
supported by any container. Therefore you need to add one
more line to your code to license wodXMPP correctly:
-
- XMPP1.LicenseKey =
"put.your.key.here"
-
| Filename |
wodXMPP.DLL (wodXMPP64.DLL for
x64) |
| Class
name |
WeOnlyDo.wodXMPPCom.1 |
| Class ID |
{19DCD07D-C515-45FD-A008-AB0D90743EDE} |
| Events class
ID |
{0x7466B8F5,0x80ED,0x4189,{0x8B,0x6C,0xB9,0xA3,0x2C,0xC4,0x67,0x9F}} |
|
Compatibility |
VB 5.0 and above, VFP
5.0 and above |
| Built
with |
Microsoft Visual Studio 2008
C++, OpenSSL |
| Required
DLLs |
None required. |
-
| Filename |
wodXMPP.OCX (wodXMPP64.OCX for
x64) |
| Class
name |
WeOnlyDo.wodXMPP.1 |
| Class ID |
{B4B4A880-C6D1-48DD-94A9-E4228072D238} |
| Events class
ID |
{0xF3C0A7C1,0x12C5,0x408B,{0x97,0x72,0x9B,0x7B,0x5F,0x2D,0x08,0x48}} |
|
Compatibility |
VB 5.0 and above, VFP
5.0 and above |
| Built
with |
Microsoft Visual Studio 2008
C++, OpenSSL |
| Required
DLLs |
None required. |
-
|
IwodXMPPNotify |
{5DD76E18-F448-41fe-9C79-71F3CC34B6F9} |
-
| Help
filename |
wodXMPP.CHM |
Distribution note
When you develop and distribute an application that uses
this component:
1. Choose between COM object (wodXMPP.DLL/wodXMPP64.DLL) and the ActiveX
control (wodXMPP.OCX/wodXMPP64.OCX) 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. wodXMPP
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 the retail (licensed) version in your code, put your
license key into LicenseKey property, immediately after
initializing the component. For the ActiveX control, you
cannot do this (there is no LicenseKey property) because
your license key will be read internally by wodXMPP.
|
