1/6/2010
The following table lists the Pocket Outlook Object Model API interfaces. They represent the 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 a city in the Cities folder. |
|
Represents a contact in the Contacts folder. |
|
Contains information about a single exception to a recurring Appointment. |
|
Provides a read-only collection of exceptions to a recurring appointment. |
|
Exposes folder properties and methods to send items in folders over an infrared link. |
|
No longer supported. |
|
This interface, derived from IRecipient, represents a new recipient item. |
|
Represents the POOM IPOutlookApp object. |
|
Represents and manages a collection of Outlook Mobile items in a folder. |
|
Represents a single member of a collection of recipients. |
|
Provides a collection of recipients for an appointment that is a meeting request. |
|
Sets the recurrence of a task or an appointment. |
|
Represents an assigned, delegated, or self-imposed task to be performed within a specified time frame in the Tasks folder. |
|
Represents a read-only object to check whether a time zone supports daylight-saving time and find when it converts between standard time and daylight-saving time. |
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.