| Home | Browse by Category | OAuth | All functions |
vuMailKit deploys as a single runtime DLL for the Basic edition.
Deploy vuMailKit.dll with your application.
The Basic edition uses a single-DLL deployment model. This DLL should reside in the same folder as your application EXE file.
If your application was built with the Clarion template, also make sure the matching import library and template files were installed at development time:
vuMailKit uses a startup initialization call for licensed use. In a normal Clarion application, the global template generates the call to vuMailKitInitialize for you.
Enter the developer license string in the template field inside single quotes:
'license-string'
The initialization call must happen before the vuMailKit Email Setup Wizard, autodetect, profile, or send functions are used. If initialization is skipped, license-gated calls return -9001 and vuMailLastError explains that the failure is a vuMailKit licensing/setup problem.
In a Clarion multi-DLL application, add the vuMailKit global template to the EXE app.
The supporting DLL apps do not need their own vuMailKit global extension. The EXE startup initializes the license for the process, and the runtime DLL is then available to send mail from code reached anywhere in the program.
Most vuMailKit functions require parameters. Create and use the proper Clarion data elements for each function. Numeric values can often be passed directly where appropriate, but string values should be placed into CSTRING variables before the function call.
The function pages in this documentation show:
The example applications and samples in the docs are also useful because they show real working flows such as:
The Demo app and vuMailKit Email Setup Wizard are good examples of using the code.
Once a managed profile has been created, vuMailKit normally uses the managed profile store under Local AppData rather than the old legacy vuMail registry model.
| Home | Browse by Category | OAuth | All functions |