Sample Applications for MAPI using MFC

This directory contains several sample applications and tools for 
MAPI 1.0, all written in C++ and using the Microsoft Foundation 
Classes. They were formerly distributed as part of the MAPI SDK, but 
were removed when the MAPI SDK was merged into the Win32 SDK.

Here is a summary list of the applications:

ABVIEW.CLI: Address book viewer application. Useful for debugging 
address book providers and clients; provides a low-level view of AB 
contents.
COMMON: This directory contains source files shared by one or more 
of the sample applications.
MDBVIEW.CLI: Message store viewer application. Useful for 
debugging store providers and clients; provides a low-level view of 
store contents.
PROPVU.CLI: Property viewer DLL. Displays the contents of an 
IMAPIProp interface in a dialog box.
SEND.CLI: Stress mailer application. Generates message traffic using 
simple MAPI; the message content is configurable.
STATUSVU.CLI: DLL for viewing provider status. Displays the status 
table and status object properties in a dialog box.
TABLEVU.CLI: DLL for viewing MAPI tables. Displays the contents 
of an IMAPITable interface in a dialog box.
XVPORT: DLL that supports a modeless window for displaying 
notifications and logging output.

Compatibility
They can be built using Microsoft Visual C++ version 2.2 for 
Windows 95 and Windows NT (Intel CPUs only); using MSVC 
version 4.0 for Windows 95 and Windows NT (all platforms); and 
using MSVC 1.52 for Windows 3.x. These samples require MAPI 1.0. 
They are compatible with all versions of the MAPI SDK, which is part 
of the Win32 SDK, and with Windows 95. They are not compatible 
with the simple MAPI implementations in Microsoft Mail 3.x, 
Windows for Workgroups, or Windows NT version 3.51 and earlier.

Installation
You must have previously installed the Win32 SDK. You will notice 
that this directory structure resembles that of the SDK MAPI sample 
tree, in \mstools\samples\mapi. Because several of the files in the 
COMMON directory duplicate those in the Win32 SDK, you should 
not attempt to overlay these files on the SDK COMMON files without 
checking them carefully for compatibility. Here is a list of the 
duplicate files:
	_scode.h
	_tags.h
	mapidbg.c
	pvalloc.c
	pvalloc.h
	wep.c
	win16.mak
	wrap3d.c
	wrap3d.h
The best thing to do is to make this directory tree a sibling of 
samples\mapi -- say, samples\mapimfc.

Compiling
To build any of the samples, change to its directory and build it using 
one of the makefiles there. The makefiles are in the same style as the 
Win32 SDK sample makefiles, and include WIN32.MAK.
	32-bit debug:	nmake
	32-bit retail:	nmake NODEBUG=1
	16-bit debug:	nmake -f makefile.16
	16-bit retail:	nmake -f makefile.16 NODEBUG=1