Share via


Differences Between the Pocket Outlook Object Model and the Outlook Object Model (Windows Embedded CE 6.0)

1/6/2010

The following topics discuss the principal differences between the Pocket Outlook Object Model and the Outlook object model.

In This Section

  • No Events
    Item events are not supported in the Pocket Outlook Object Model (POOM).
  • No NameSpace Object
    Unlike the desktop version of the Outlook object model, there is no NameSpace in Pocket Outlook Object Model (POOM). The required logon functionality is merged with the POOM IPOutlookApp object.
  • Outlook Compatibility
    The IPOutlookApp::get_OutlookCompatible method provides a way for independent software vendors to find out if the Windows Embedded CE-based device has a device partnership with a desktop computer that is running Microsoft Schedule+ for Windows 95, or Microsoft Outlook. The main reason is that there is a difference in the behavior of Task items. When your device has a partnership with a desktop computer that is running Microsoft Schedule+, Tasks with a Start Date of None must also have a Due Date of NONE. Recurrences of the Tasks are computed with respect to the Due Date. When your device has a partnership with a desktop computer that is running Outlook, recurrences of Tasks are computed only with respect to the Start Date.
  • Recipients Define Meeting Requests
    In the Outlook Object Model, you set an Appointment's OlMeetingStatus property to mark it as a Meeting Request. As a result, you can create Appointment items that have a Recipient List but are not Meeting Requests. This is not possible on Windows Embedded CEā€“based devices.

    In the Pocket Outlook Object Model (POOM), an Appointment is a Meeting Request if it has a IRecipients collection. The IAppointment::get_MeetingStatus method returns the OlMeetingStatus enumeration values of either olNonMeeting or olMeeting.

    The IRecipient::get_Address method returns a read-only version of the recipient's e-mail address, and the IRecipient::put_Address method accesses a writable version. In the desktop version of Outlook, the same property returns a read-only version. There is no writable version because there is no IPOlRecipient::Resolve method in the desktop version of Outlook (which matches a Recipient's first and last names with Contact names in the data store).

  • **

See Also

Other Resources

Pocket Outlook Object Model Application Development