What's New in This Edition
The Microsoft Office Outlook 2007 MAPI Reference documentation has been updated to make it more complete, accurate, and useful. Many new topics have been added, all the topics have been reviewed and updated, and a few obsolete topics have been removed.
The following content has been added:
More properties There are now close to 900 properties documented, including tagged properties and named properties.
More code samples New code samples have been added to show how to use MAPI to create various Outlook items. MFCMAPI is referenced as a sample application in many concept and reference topics showing specific code files and functions that demonstrate how particular APIs are used. New code samples have also been added to MFCMAPI for this purpose.
The following changes have been made to improve the usability of the documentation:
Property names Canonical property names, which use "PidTag", "PidLid", and "PidName" prefixes, provide consistent naming. Canonical property names better identify related properties. The topics Mapping Canonical Property Names to MAPI Names and Mapping MAPI Names to Canonical Property Names show the association between canonical property names and real property names.
Updated samples Code samples for three major MAPI service providers (address book, message store, transport) are updated for Microsoft Visual Studio 2008 and are available on CodePlex. For more information, see Downloading the Outlook 2007 MAPI Samples. Documentation for the samples is at MAPI Service Provider Samples.
Content scrub All topics have been updated to include the latest technologies and products.
Documentation for Simple MAPI and the MAPI stub library is now published as part of the Microsoft Windows documentation on MSDN.
The following obsolete content has been removed:
Common Messaging Calls (CMC).
The hook provider and preprocessor.
Collaboration Data Objects (CDO) — the Outlook 2007 Object Model unites various APIs, including CDO 1.2.1.
Mapidbg.ini — Microsoft no longer ships this file, because there is no debug build of MAPI.
Newprof.exe — Microsoft no longer ships this file. The supported method for creating PRF files is to use the Office Customization Tool.
Mbdvu.exe/mbdvu32.exe — Developers should use MFCMAPI to do testing.