Export (0) Print
Expand All

Outlook 2010 MAPI Reference Overview

Last modified: April 19, 2011

Applies to: Office 2010 | Outlook 2010 | Visual Studio

This topic provides overview information about the Microsoft Outlook 2010 MAPI Reference documentation.

This documentation applies to the implementation of the Messaging API (MAPI) in Microsoft Outlook 2010.

Previous to Microsoft Office Outlook 2007, the MAPI Programmer's Reference was part of the Microsoft Exchange documentation.

Note Note

Because Exchange has deemphasized the use of MAPI since Microsoft Exchange Server 2007, support for the Exchange implementation is limited.

The Outlook implementation of MAPI differs from the Microsoft Exchange implementation. The Outlook implementation is optimized for running on client computers and emphasizes low latency. The Exchange implementation is intended for servers where high availability and better multithreading are important.

Use this documentation for applications running on end-user systems. For server applications, use the Exchange implementation of MAPI, if appropriate, or use current Exchange APIs, such as Exchange Web Services. For more information on Exchange Web Services, see the Exchange Web Services Reference.

It may be possible to write applications that work with either the Outlook or Exchange implementations of MAPI. For example, MFCMAPI works well on either platform. The implementations have many common features, but there are differences both obvious and subtle. You will have to test carefully on both platforms if you intend for your application to work in all environments. This testing will require two systems, because running both implementations on the same operating system installation is not supported.

Be aware that MAPI is appropriate for low-level access to data in a MAPI store or for building a transport, message store, or address book provider. Because MAPI bypasses Outlook’s business logic, you should also consider the use of the Outlook object model when you evaluate APIs for building your solution. The Outlook object model does encapsulate Outlook business logic, but is not suitable for multithreaded code, sync providers, or Windows Service applications.

For information about what is new in this edition, see the following topics:

If you are new to developing MAPI applications for Outlook, see the following topics:

The rest of this reference is categorized into the following three types of information:

  • MAPI Samples directs you to many code samples that show the use of various API elements, and how to implement basic MAPI providers and create Outlook items.

  • MAPI Concepts explains the concepts and architecture of MAPI.

  • MAPI Reference provides detailed information about the functions, interfaces, structures, and properties in MAPI.

Community Additions

ADD
Show:
© 2014 Microsoft