| Home | All functions | Categories |
vuMailKit deploys as a single runtime DLL for the Basic edition.
Deploy vuMailKit.dll with your application.
The Basic edition now 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.lib for linkingvuMailKit.tpl for the template integrationMost 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 Email Client Wizard are good examples of using the code.
vuMailKit uses a startup initialization call for licensed use. In a normal Clarion application, call vuMailKitInitialize() once during EXE startup before you invoke the wizard, autodetect, or send functions.
The template-generated startup code is the normal way to handle this.
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.
vuMailKit.lib import library.vuMailKit.dll with the EXE.vuMailKitInitialize().| Home | All functions | Categories |