I programmatically add a user property to an appointment before I send it to
a recipient. This is done via a Windows Form (using VSTO) launched from an
Outlook tool bar.

appointment.UserProperties.Add("ExamplePropertyNam e",
Outlook.OlUserPropertyType.olText, true, Outlook.OlUserPropertyType.olText);
appointment.UserProperties["ExamplePropertyName"].Value =
"ExamplePropertyValue";
appointment.Save();

However, the user property is not propagated to the recipient. I am
wondering if it is related to this KB article:

http://support.microsoft.com/kb/907985

But adding custom properties programmatically is listed as a best practice
and I am not using Outlook forms at all.

Do I have to use the AllowNamedProps registry key as well?

The problem with appointments is that when you send a meeting
request/updatee, Outlook creates a meetign request item 9separate from teh
appointment), populates the properties that it knows about, and then sends
it. The original appointments stays in teh Calendar folder.
Since it knowns nothing about your custome properties, it does not copy them
to the mettign request/update.

--
Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool
-
"Tadwick" wrote in message
...
I programmatically add a user property to an appointment before I send it
to
a recipient. This is done via a Windows Form (using VSTO) launched from
an
Outlook tool bar.

appointment.UserProperties.Add("ExamplePropertyNam e",
Outlook.OlUserPropertyType.olText, true,
Outlook.OlUserPropertyType.olText);
appointment.UserProperties["ExamplePropertyName"].Value =
"ExamplePropertyValue";
appointment.Save();

However, the user property is not propagated to the recipient. I am
wondering if it is related to this KB article:

http://support.microsoft.com/kb/907985

But adding custom properties programmatically is listed as a best practice
and I am not using Outlook forms at all.

Do I have to use the AllowNamedProps registry key as well?