How to Create a Messaging Application
Windows Mobile-based messaging applications are built using interface members belonging to the Messaging API (MAPI). MAPI definitions are referenced in the Cemapi.h header file, and are implemented in the Cemapi.lib file. This section contains topics that present procedures with code examples that show you exactly how to use MAPI to create a messaging application.
In this Section
- How to: Begin a MAPI Session
Before you can access a message store, you must initialize the MAPI subsystem and log onto a MAPI session. This gives you a referfence to an IMAPISession interface object, which you can use to access the message store table, message stores, message folders, and messages. - How to: End a MAPI Session
When the user is done performing messaging tasks, there is no further need to consume valuable system resources with the messaging subsystem. At this point, it is a good idea to free resources by ending the MAPI session. - How to: Connect to a Message Store
Before you can create and manipulate message folders and message items, you must establish a connection to a message store. - How to: Create a Message
New messages are always created from a message store's Drafts folder. After you create a message, you can set its property values (subject, body, list of recipients, and so on) and then send the message. - How to: Send a Message
New messages are always created and sent from a message store's Drafts folder. After you create a message, you set its property values (subject, body, list of recipients, and so on) and then post the message. - How to: Register Customized Messaging Forms
Customized messaging forms require two separate registry entries. The first one registers the form COM server as a message class. This gives the Messaging application the information it needs to locate the plug-in DLL and extract the read and compose forms for displaying and creating messages. The second entry specifies the message transport(s) to use. - How to: Register Customized Messaging Transports
Customized messaging transports require one registry entry. It specifies the name for the new message transport, along with the name of the DLL that contains it - How to: Register Customized Messaging Rules Clients
Customized messaging rules clients require two separate registry entries. The first one registers the messaging rules client as a COM server, specifying its GUID. The second entry specifies the message transport(s) to use.
See Also
Messaging Application Development for Windows Mobile-based Devices
Send Feedback on this topic to the authors