-
-
General
wodMailbox component has two versions (both included in the
package):
-- wodMailboxCom is a COM object (wodMailbox.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 Mailbox1 as wodMailboxCom
and wodMailbox as ActiveX control (wodMailbox.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 wodMailbox, of course), you need one more line
to put in your code to license wodMailbox correctly:
-
- Mailbox1.LicenseKey =
"put.your.key.here"
-- If you directly initialize Message object instead of
Mailbox, you must also set LicenseKey property manually,
otherwise you will not be able to use Message object at
all! Typical scenario would be when you want to use Peek on
standalone, one-message-per-file message.
- Dim Msg As
WODMAILBOXCOMLib.Message
Set Msg = New WODMAILBOXCOMLib.Message
Msg.LicenseKey = "put.your.key.here"
m.Peek App.Path + "\.........."
-
| Filename |
wodMailbox.DLL
(wodMailbox64.DLL for x64) |
| Class
name |
WeOnlyDo.wodMailboxCom.1 |
| Class ID |
{AF1B055F-C0C7-4504-AA82-F0E21549E7E2} |
| Events class
ID |
none |
|
Compatibility |
VB 5.0 and above, VFP
5.0 and above |
| Built
with |
Microsoft Visual Studio 2008
C++ |
| Required
DLLs |
none |
-
| Filename |
wodMailbox.OCX
(wodMailbox64.OCX for x64) |
| Class
name |
WeOnlyDo.wodMailbox.1 |
| Class ID |
{7275158F-33FA-472E-8383-844D5D9BD206} |
| Events class
ID |
none |
|
Compatibility |
VB 5.0 and above, VFP
5.0 and above |
| Built
with |
Microsoft Visual Studio 2008
C++ |
| Required
DLLs |
none |
-
|
IAttachment |
{DC181523-CA68-4413-830F-AB7954E18340} |
|
IAttachments |
{8264F3C4-16DD-4073-B195-2939C5569E62} |
| IDecoder |
{636ACB7E-2BCC-4EE1-BF3A-E00A32F114A3} |
| IEncoder |
{D3BF6DEA-82F7-41B1-90F5-D682C318E07A} |
| IHeader |
{0D37E9B9-3873-4D96-AD2B-1ACDBA751554} |
| IHeaders |
{559D5757-4C63-4E46-A732-4B44BE8DFA8E} |
| IMessage |
{E519C99F-AF02-4B6B-A774-6267F89BD766} |
| IMessages |
{DF90E178-02E2-44DB-AAA3-711FF12D32F6} |
-
| Help
filename |
wodMailbox.CHM |
Distribution note
When you develop and distribute an application that uses
this component:
1. Choose between COM object (wodMailbox.DLL/wodMailbox64.DLL) and the
ActiveX control (wodMailbox.OCX/wodMailbox64.OCX) to include into the
installation package. Both versions are independent on each
other.
2. Above binaries can be included royalty-free in your
application.
3. 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
4. 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 wodMailbox.
|
