docs

Home Getting Started Browse by Category All functions

What Most Developers Actually Use

vuMailKit includes many functions, but most developers do not need most of them for everyday mail sending.

A large part of the library exists for:

For normal outbound email, start with the shortest path that works.

The common workflow

In many cases, this is all you need:

  1. Add the global template to the EXE app.
  2. Enter the developer license string in single quotes.
  3. Use CTRL+U to import the vuMailKit Email Setup Wizard.
  4. Compile the application.
  5. Run the compiled EXE.
  6. Run the vuMailKit Email Setup Wizard, send a test email, and save the profile.
  7. Call a send function.

Once the vuMailKit Email Setup Wizard succeeds and the profile is saved, the profile is ready to use.

That is a major simplification compared with older usage patterns where developers expected to keep filling in server settings manually. A normal Send button can then follow the recommended send flow: check for a saved profile, offer the wizard if needed, validate the recipient, send, and show useful diagnostics.

What most developers usually touch first

The first things many developers care about are:

That is why the Getting Started section is task-based.

Simple HTML is the first HTML path to try

Simple HTML mode can make an ordinary text body look like a clean HTML message without requiring you to build a full HTML wrapper.

For ordinary text from a TEXT control, TPS memo, customer note, generated report, or similar field, turn Simple HTML on, keep NormalizeBody on, and pass the text as-is. vuMailKit converts existing line breaks for HTML display.

If you also need images inside the message body, do not type raw HTML image tags into the normalized text. Put the embed-attachments marker where the images should appear and pass local image files or remote http/https image URLs in the Attach parameter. vuMailKit replaces the marker with inline images and still treats the rest of the body as ordinary text.

Start here:

TokenMerge is already built in

TokenMerge gives you reusable mail-merge behavior without making every developer reinvent it.

Use it when you want to replace tokens in memory, replace tokens while copying a template file to an output file, or insert generated text-file content into an HTML email template.

Start here:

When the larger function library matters

The broader function library becomes useful when you need:

Those features matter, but they do not have to be learned first.

Recommendation

Start with the simplest successful path first:

Then branch out only when you need more.

Home Getting Started Browse by Category All functions