-
-
General
wodPop3 component has two versions (both included in the
package):
wodPop3Com is a COM object (wodPop3.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
- Dim WithEvents Pop3 as wodPop3Com
and wodPop3 as ActiveX control (wodPop3.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.
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 wodPop3, of course), you need one more line to
put in your code to license wodPop3 correctly:
-
- Pop3.LicenseKey =
"put.your.key.here"
-
| Filename |
wodPop3.DLL (wodPop364.DLL) |
| Class
name |
WeOnlyDo.wodPop3Com.1 |
| Class ID |
{E5040898-D12B-40B1-AB61-9317CAF04E75} |
| Events class
ID |
{0xC075109C,0x4261,0x4398,{0xA8,0x98,0x9E,0x28,0xE2,0x5F,0xBF,0xDC}} |
|
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. |
-
| Filename |
wodPop3.OCX (wodPop364.OCX) |
| Class
name |
WeOnlyDo.wodPop3.1 |
| Class ID |
{BADA040D-0D14-4EAB-BB49-774C637DB2BC} |
| Events class
ID |
{0xF568542E,0x31F7,0x4AF9,{0x9B,0x78,0x31,0x44,0xED,0x0F,0x5F,0xA9}} |
|
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. |
-
|
IPop3Attachment |
{AFE840E3-96D3-4131-AE1C-832DCE446F2E} |
|
IPop3Attachments |
{F8D0C026-B004-4A48-BB69-CF0380CA9470} |
|
IPop3Decoder |
{7637298F-5132-48FC-A5F9-5C3EC2986B0E} |
| IPop3Hdr |
{0437D23A-4480-412E-83A9-CBB5B0FD99C6} |
| IPop3Hdrs |
{401487AE-4399-48E2-AD66-5F84B2CCFD26} |
| IPop3Msg |
{385148FE-561C-4D94-AD1F-3E33395528BD} |
| IPop3Msgs |
{C04E36C2-ED40-40F3-98BD-72D1DB231910} |
|
IwodPopClientNotify |
{8122F26D-CA23-4722-89D9-44BBEB4ACCAB} |
-
| Help
filename |
wodPop3.CHM |
Distribution note
When you develop and distribute an application that uses
this component:
1. Choose between COM object (wodPop3.DLL/wodPop364.DLL) and the ActiveX control
(wodPop3.OCX/wodPop364.OCX) to include into the installation package. Both
versions are independent on each other.
2. You should include wodCertificate.DLL/wodCertifiate64.DLL for Certificate management
- if it is needed in your application. wodFtpDLX 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 wodPop3.
|
