Windows Mobile devices include a messaging subsystem that enables them to be used for sending, receiving, storing, and manipulating e-mail and SMS text messages. The Microsoft messaging client application, Messaging (formerly named Inbox), provides the user interface for composing and reading messages, and for accessing and manipulating the message items contained in local and remote message stores. The Windows Mobile version of the Messaging API (MAPI) is called CEMAPI, and it is a COM-based type library that provides programmatic access to all of this functionality and more.
To create a messaging application, your Visual Studio project must include the header file cemapi.h, and it must also link to the type library file cemapi.lib.
CEMAPI mirrors the Exchange Server version of MAPI, but covers a smaller scope of functionality to accommodate the practical constraints of mobile devices. For more information see MAPI Evaluation Criteria in the MSDN Library.
In This Section
- Messaging Application Development
Covers the background information about the Messaging subsystem, the Messaging Application, and the CE Messaging API (CEMAPI). Explains SMTP servers, message stores, messaging transports, messaging accounts, configuration, and customization. This section also contains a comprehensive set of "How to" topics that demonstrate the steps in creating a CEMAPI-based application.
- Messaging Migration
Information about migration issues in messaging.
- Messaging Common Tasks
Contains procedures with code examples that show you exactly how to use CEMAPI to create a messaging application.
- Messaging Security
Information on security issues in messaging.
- Messaging Samples
Lists the CEMAPI-related code samples that ship with the Windows Mobile Classic and Windows Mobile Standard SDKs—each of which demonstrates a particular aspect of CEMAPI functionality.
- Messaging API (CE MAPI) Reference
Provides reference information on the interfaces, enumerations, constants, and flags, that make up the CE Messaging API (CEMAPI).
- Pocket Outlook Object Model (POOM)
POOM is a COM-based library that provides programmatic access to Outlook Mobile data items. It provides an object-oriented framework for creating, modifying, and displaying appointment, task, and contact items — and for manipulating the folders that contain them. Note: Outlook Mobile uses the messaging subsystem to send meeting requests, and to assign tasks to recipients.
- Short Message Service (SMS) API
The SMS API is a COM-based library that provides programmatic access to SMS text messaging functionality.
- Creating Themes
Contact cards include theme primitives when themes are implemented on a Windows Mobile Professional phone. See the Themes and Contact Cards section for more information.