Pocket Outlook Object Model (POOM) (Windows Embedded CE 6.0)
The Pocket Outlook Object Model (POOM) mirrors the Microsoft Office Outlook Object Model, but its scope of functionality is reduced to accommodate the practical constraints of mobile devices. POOM is a COM-based library that provides programmatic access to Outlook Mobile Personal Information Management (PIM) data items and container objects. It provides an object-oriented framework for creating, modifying, and displaying appointment, task, and contact items—and for manipulating the folders that contain them.
For information about the Microsoft Office Outlook Object Model, see this Microsoft Web site.
|The set of POOM APIs that ship as part for Windows Embedded CE is also known as POOM1.|
- Pocket Outlook Object Model OS Design Development
Gives an overview of the modules and components that implement POOM, and the sysgen variables that enable this functionality.
- Pocket Outlook Object Model Application Development
Provides a description of the Outlook Mobile Application object, the entry point into the POOM.
- Pocket Outlook Object Model Migration
Details the requirements and caveats related to porting code that was written for earlier versions of POOM, to more recent versions of POOM.
- Pocket Outlook Object Model Common Tasks
Contains a series of hand-on style topics that demonstrate how to create POOM applications.
- Pocket Outlook Object Model Security
Provides security information regarding POOM, and best practices for implementation.
- Pocket Outlook Object Model Samples
Describes working code samples that use the POOM APIs.
- Pocket Outlook Object Model Reference
Contains the POOM API reference pages, which detail all of the POOM programming elements (interfaces, functions, enumerations, etc.).
- The Desktop Version of the Outlook Object Model
Visit the Microsoft Office Solutions Developer section on MSDN to see how the Outlook Object Model is implemented on the desktop and by Exchange Server.
- Exchange Client
Contains technical details about the interfaces, constants, structures, and enumerations, that make up the Exchange Client API. You can use this API to create Windows Embedded CE-based applications that interact with an Exchange Server.