The model for add-in development for MFCMAPI is quite simple. Build a DLL that exports a few functions, drop said DLL into the same directory as MFCMAPI, and MFCMAPI will find it when it starts up. No messy config files, no fiddling around in the directory. Wanna disable an add-in? Just rename it so it’s not a DLL anymore.
The core of an MFCMAPI addin is the header file: MFCMAPI.h. This file contains the definitions for the functions you’ll need to implement and export from your DLL, as well as definitions for functions your add-in can import from MFCMAPI.
To get you started, here’s a test add-in: TestAddIn.zip. It doesn’t do much except exercise the various add-in entry points. It was developed in sync with the addition of add-ins to the code base as part of my testing.
Stuff the Add-In implements
This function lets the add-in know we’re here and get its name. You have to implement this one for MFCMAPI to know you’re an add-in.
MFCMAPI will call this when unloading add-ins. This is a good time to free resources.
Return an array describing the menu entries you’d like to have, when you want them to be enabled, and what information you want passed back to you when your menu is invoked.
Let’s you know one of your menu items has been selected, along with a wealth of contextual information.
Return an array of property names for MFCMAPI to use in decoding properties.
Return an array of property types for MFCMAPI to use in decoding properties.
Return an array of property guids for MFCMAPI to use in decoding properties.
Returns an array of named property mappings for MFCMAPI to use in decoding properties.
Return an array of flag parsing information for MFCMAPI to use in decoding properties.
Stuff MFCMAPI implements
Call this to generate debug output through MFCMAPI’s own logging routines.
A quick and dirty dialog.
A harder to use, but much more featured dialog that can be used to get user input.
If you use ComplexDialog, you might get a structure back with the results. This function frees that structure.
Get a handle to the MAPI binary that MFCMAPI loaded, or ask MFCMAPI to go ahead and load MAPI.
A well behaved add-in will not link mapi32.lib. Instead, it will use GetMAPIModule to get a handle to MAPI, then GetProcAddress to get any exports you need. The reason for not statically linking is to allow MFCMAPI the flexibility to load MAPI itself from custom locations.
Also, a well behaved add-in is not written in .Net, since MAPI and .Net aren’t supported in combination. No bugs will be taken on this.