Best practices for synchronizing custom properties of PocketOulook.PimItem

I'm working on a managed (C#) Windows Mobile 5.0 Application that
manipulates Custom Properties of PimItem (Appointment) objects.

Problem:
It seems that neither Outlook User Properties nor PocketOutlook custom
properties are synchronized to the Exchange 2003 Server by ActiveSync

Work-around:
My current work-around serializes the custom properties into the PimItem
(Appointment) body,
although this method works, it's not aesthetically pleasing for our desktop
users because a blob of XML is visible when these appointments are viewed in
outlook, additionally it may make the application more susceptible to
user-error's because of the possibility of unintentionally editing the XML
blob in the body of the appointment.

Question:
What are best practices for:
1. saving "Custom Properties" to a PocketOutlook PimItem
2. having these properties propagated by ActiveSync to an Exchange Server
3. accessing such properties from a managed Desktop application, or Exchange
Store Sink


Joris van Lier

Hi,
Unfortunately, there is no support to sync custom properties or custom
fields with Exchange ActiveSync or ActiveSync on your PC. The workaround
you are using is the best one I have heard of.


--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.pocketpctalk.com
http://www.tabletpctalk.com
http://www.mobilitytalk.com

"Joris van Lier" <> wrote in message
newsEBA5EB9-1858-494D-9CF8-...
> I'm working on a managed (C#) Windows Mobile 5.0 Application that
> manipulates Custom Properties of PimItem (Appointment) objects.
>
> Problem:
> It seems that neither Outlook User Properties nor PocketOutlook custom
> properties are synchronized to the Exchange 2003 Server by ActiveSync
>
> Work-around:
> My current work-around serializes the custom properties into the PimItem
> (Appointment) body,
> although this method works, it's not aesthetically pleasing for our
> desktop users because a blob of XML is visible when these appointments are
> viewed in outlook, additionally it may make the application more
> susceptible to user-error's because of the possibility of unintentionally
> editing the XML blob in the body of the appointment.
>
> Question:
> What are best practices for:
> 1. saving "Custom Properties" to a PocketOutlook PimItem
> 2. having these properties propagated by ActiveSync to an Exchange Server
> 3. accessing such properties from a managed Desktop application, or
> Exchange Store Sink
>
>
> Joris van Lier