Pocket Outlook Object Model Interfaces (Compact 7)
3/12/2014
The following table lists the Pocket Outlook Object Model (POOM) API interfaces. They represent the Personal Information Manager (PIM) items, item collections, storage folders, and recurrence patterns that make up the object model.
Programming element | Description |
---|---|
Represents an appointment in the Calendar folder. |
|
Represents an appointment in the Calendar folder. |
|
Provides the callback sink for receiving change notifications from item stores. |
|
Represents a city in the Cities folder. |
|
Represents a contact in the Contacts folder. |
|
Represents a contact in the Contacts folder. Its methods can be used to save, delete, duplicate, or display a contact. |
|
Represents an event sink for custom events from the Unified Item Store. |
|
Contains information about a single exception to a recurring appointment. |
|
Provides a read-only collection of exceptions to a recurring appointment. |
|
Exposes properties and methods for creating and accessing individual POOM items, and for sending them over an infrared link. Note While the POOM has methods related to infrared communication, Windows Embedded Compact 7 does not support the use of infrared hardware. |
|
Exposes properties and methods for creating and accessing individual POOM items, and for sending them over an infrared link. Note While the POOM has methods related to infrared communication, Windows Embedded Compact 7 does not support the use of infrared hardware. |
|
Represents a generic PIM item. |
|
Represents a generic PIM item. |
|
Represents a PIM configuration manager, which third-party applications use to register a PIM provider with PIM applications. |
|
Represents a contact summary card. |
|
Represents a newly updated contact card. |
|
Represents a PIM item. |
|
Represents a collection of PIM items, and provides access to PIM item properties for an item at a given index within a collection, without the need to instantiate the item. |
|
Represents a collection of PIM items. |
|
Provides the IPOlRecipient::Resolve method, which matches first and last names of a recipient against the Contact items in the data store. |
|
Represents the Outlook Mobile application object. |
|
Provides access to PIM items, their custom properties, and their folders. |
|
Represents the Outlook Mobile application object. |
|
Represents a collection of POOM Folder items. |
|
Represents and manages a collection of PIM items contained in a folder. |
|
Represents and manages a collection of PIM items contained in a folder. |
|
Represents a collection of POOM item stores. |
|
Represents a single member of a collection of recipients. |
|
Supports synchronizing Meeting Attendee Type and Meeting Attendee Status. |
|
Represents the recipient details associated with a meeting request. |
|
Provides a collection of recipients for a meeting request (that is, an Appointment with a list of recipients). |
|
Represents the recipient table in the POOM item store. |
|
Provides read-write access to recurrence pattern objects associated with Task and Appointment items. |
|
Provides read-write access to recurrence pattern objects associated with Task and Appointment items. |
|
Represents a POOM item store (object database). |
|
Represents an assigned, delegated, or self-assigned task to perform within a specified time frame. |
|
Represents an assigned, delegated, or self-assigned task to perform within a specified time frame. |
|
Provides read-only access to standard and daylight saving time-zone information. |
Remarks
Although all of the POOM interfaces inherit the IDispatch interface, using the IDispatch methods (IDispatch::GetIDsOfNames, IDispatch::GetTypeInfo, IDispatch::GetTypeInfoCount, and IDispatch::Invoke) on POOM objects is not supported.
See Also
Reference
Pocket Outlook Object Model Reference