What's New in This Edition

Last modified: November 05, 2011

Applies to: Office 2010 | Outlook 2010 | Visual Studio

The Microsoft Outlook 2010 MAPI Reference has been updated to include documentation for various new features.

Content has been added for the following features:

  • Using Microsoft Outlook 2010 and 64-bit MAPI requires more than the traditional 32-bit API for full implementation. The MAPI Stub Library, posted on the CodePlex website, provides a drop-in replacement for Mapi32.lib that supports building both 32-bit and 64-bit MAPI applications. For more information, see How to: Link to MAPI Functions and CodePlex.

  • The section Getting Started with the Outlook 2010 MAPI Reference has been updated to reference comprehensive information about programming models for your Outlook and MAPI functionality to help you identify the APIs and technologies that are most appropriate for your needs.

  • Autocomplete Stream—The Nickname cache topic, formerly the Nk2 File Format, has been updated to reflect changes in Outlook 2010. Information such as the autocomplete list, which is the list of names that displays in the To, Cc, and Bcc edit boxes while a user is composing an email, is now saved to the Autocomplete Stream of a message on the local computer rather than saving it to a file as in Outlook 2007.

    • Interacting with the Autocomplete Stream

    • Loading the Autocomplete Stream

    • Saving the Autocomplete Stream

  • MAPI Constants—The MAPI Constants have been consolidated. In previous releases they were distributed in a number of topics and now they are collected in a single topic to make them easier to discover and use.

  • Personal Store Override—The following interfaces and their respective methods have been added to support overriding the Personal Folders file (PST) store providers PSTDisableGrow policy.



  • Properties—The following tagged properties have been added:

Content was added in the previous release of the Microsoft Outlook 2010 MAPI Reference for the following features:

  • Support for 64-bit Microsoft Outlook—Reference topics for applicable API elements were updated to correspond to new header files that support 64-bit Outlook. These header files are available as a download at Outlook 2010: MAPI Header Files. A new code sample was provided in How to: Check the Version of Outlook to show how to check whether the installed version of Outlook is 64-bit Microsoft Outlook 2010. If your existing 32-bit MAPI application is going to be running on a 64-bit operating system with 64-bit Outlook installed, you will need to rebuild your 32-bit application as a 64-bit application. For more information about MAPI support for 64-bit Outlook, see Building MAPI Applications on 32-Bit and 64-Bit Platforms.

  • Fast shutdown support for MAPI clients—MAPI clients can now initiate a quick shutdown and have the MAPI subsystem notify loaded providers to minimize data loss from the fast shutdown. Additional interfaces were added for the client and provider to support fast shutdown. For more information about fast shutdown, see Client Shutdown in MAPI.

  • Stream structure for field definitions for an Outlook item—Documentation for a binary stream for the PidLidPropertyDefinitionStream property was added. This property specifies definitions of all custom fields and data-binding settings for built-in fields of an Outlook item.

  • More properties—Documentation for an additional 38 tagged properties and named properties was added.

  • Option of linking explicitly to MAPI functions—MAPI developers can now choose to explicitly link to the MAPI stub of the default MAPI client (for example, Msmapi32.dll of Outlook) without going through the MAPI library and the Windows MAPI stub. For more information about explicit linking as compared with implicit linking, see How to: Link to MAPI Functions.

  • Message Store Provider Example—The Sample Wrapped PST Store Provider Example was updated to support 64-bit architecture.

  • Using Multiple Exchange Accounts—Documentation for the MAPI Address Book API was added. This API has been enhanced to support multiple Exchange accounts in Microsoft Outlook 2010. To resolve addresses correctly with multiple Exchange accounts, use the new functions that take an account context so that calls to the address book search the correct Exchange account.