Getting Started (Outlook 2010 Auxiliary Reference)

The Microsoft Outlook 2010 Auxiliary Reference contains conceptual content and reference documentation for four sets of APIs, code samples, and a redistributable installer that allow developers to extend and integrate with Microsoft Outlook 2010. APIs in this reference are exposed by Outlook for extensibility, outside of the Outlook object model.

If you are new to developing solutions for Outlook, see Selecting an API or Technology for Developing Outlook Solutions to identify the APIs and technologies that are most appropriate for your needs. For specific information about the Outlook object model, see the Outlook 2010 Developer Reference. For specific information on Messaging API (MAPI) supported by Outlook, see the Outlook 2010 MAPI Reference.

The conceptual discussion includes the following subjects:

• About Anti-Spam Settings

• About Conflict Resolution for Custom Item Types

• About the Last Update Time of an Offline Address Book

• About Registering a New Domain for Automatic Configuration

• About Meeting Requests as Informational Updates and Full Updates

• About Rebasing Calendars Programmatically for Daylight Saving Time (There is also a redistributable installer for third-party calendar rebasing tools. To download the installer, see Outlook 2010: Auxiliary Reference Redistributable Installer and Header File for Rebasing Calendars.)

• About Persisting TZDEFINITION to a Stream to Commit to a Binary Property

The reference content includes the following:

• The APIs Exported by Outlook include functions and data structures that were originally implemented for internal use and are now exposed for public use.

• The Account Management API provides access to user account information and notifications of account changes.

• The Data Degradation Layer API supports clients that access an Outlook item in a preferred character format rather than the object's native character format.

• The Free/Busy API provides free/busy status information about specific user accounts within a specific time range.

• Sample how-to tasks in the Outlook 2010 Auxiliary Reference include the following:

  • How to: Determine Whether an Outlook Item Has Been Modified but Not Saved (Outlook 2010 Auxiliary Reference)

  • How to: Parse a Stream from a Binary Property to Read the TZDEFINITION Structure

  • How to: Parse a Stream from a Binary Property to Read the TZREG Structure

  • How to: Read Time Zone Properties from an Appointment

  • How to: Specify Whether to Display a Contact's Picture in Outlook (Outlook 2010 Auxiliary Reference)

  • How to: Use Relative Time to Access Free/Busy Data

The reference for each API lists the constants, type definitions, and interfaces that a developer must implement to use the additional functionality.

Note

Developers must implement these APIs only as documented in this reference. Certain interface members and method parameters are named as placeholders because they are reserved for the internal use of Outlook and are subject to change without notice.