Design Goals (Windows CE 5.0)
POOM supports the following goals:
Backward Compatibility
POOM runs on Microsoft® Windows® CE 3.0.
Forward Extensibility
The interfaces are designed to be extensible. For example, the Folder object is simply a wrapper around a database. Backward compatibility prohibits creating or manipulating these folders.
Outlook Compatibility
There are changes from the desktop Outlook Object Model to achieve simplicity on the Windows CE-based device. For example, there is no NameSpace object, which Outlook uses to log on to a MAPI session, but would just be an extra layer on Windows CE–based devices.
It is more accurate to say that POOM is based on the Outlook Object Model than to say it is a subset of the model. For more information about other differences between the desktop and Windows CE-based device versions, see Differences Between the Windows CE and Desktop Models.
Automation Object
To permit Microsoft Visual Basic® and script programming, the object model automation has a dual interface. Although the method and property names are slightly more complicated in Microsoft Visual C++® than they are in Visual Basic, POOM is now available to a wider range of developers.
Simplicity
The interfaces are meant to be simple, and therefore represent a sparse subset of the Outlook Object Model. However, some compromises were necessary. For example, the Display method only works on items that have not been modified through the application programming interface (API) set, and in some cases, you cannot access the information you have added after calling this method. The reason is that, for simplicity, POOM sits on top of existing or unexposed functions internal to the Personal Information Manager (PIM) applications, and these functions do not allow this functionality.
See Also
Pocket Outlook Object Model Application Development
Send Feedback on this topic to the authors