I'm testing with the evaluation version of the 3.1 InTheHand.WindowsMobile.PocketOutlook library.  I'm finding that when I try get the MeetingOrganizerName it is always = ""(empty string).   Same result referencing the Properties collection like

    app.Properties[AppointmentProperty.MeetingOrganizerName]

Also I get an ArgumentException when trying define an new custom property for an Appointment like:

    Appointment app= new Appointment;

    app.Properties["MyProperty"]=6

 I get the same exception whether I create a new appointment or modify an existing appointment.  Same result even if a call all on the Properites collection and specify the correct Type.

Let me know

Thanks

Dan 

The MeetingOrganizerName is not present on all meeting items and requires Windows Mobile 6.

Before you can write a custom property you must first call Add to setup a property with the required name e.g.

 app.Properties.Add("MyProperty", typeof(int));

Peter

 With the InTheHand.WindowsMobile.PocketOutlook library running on WM 5 SmartPhone

 app.Properties["MeetingOrganizerName"]  does return "" (empty string)

 Same device and same code using the Microsoft.WindowsMobile.PocketOutlook library does return the name of the organizer

======================= 

Running this code with the InTheHand.WindowsMobile.PocketOutlook library running on WM 5 SmartPhone throws an ArgumentException on the second line (setting the value of the property)

            app.Properties.Add("MyProperty", typeof(int));
            app.Properties["MyProperty"] = (int)100;
            MessageBox.Show(app.Properties["MyProperty"].ToString());

 Same device and same code using Microsoft.WindowsMobile.PocketOutlook library shows the value of 100.

Is there something I need to do to initialize the custom properties collection?

Let me know

Thanks

Dan 

I'm currently finding the MeetingOrganizerName by passing the appointment's ItemId to a C++ dll then finding the item by id and then looking into the properties collection.  Although this approach works it is an expensive operation since I need to instantiate the appointment in the unmanaged code.

Let me konw

Thanks

Dan 

I'm investigating this and will have a fix for the next release v3.2 which will be available soon.

Peter

We're upgrading from 3.1 to 3.3 and we're seeing that the custom properties bag seems to work very well.  Thank you.  

I'm still seeing an issue where Appointment.Properties[AppointmentProperty.MeetingOrganizerName] is null for for specific meeting/appointments but if I reference the same appointments via the Microsoft.PocketOutlook library or using Native POOM (using PIMPR_MEETING_ORGANIZER_NAME) I can retrieve the organizer name/email.

Have you noticed anything in common with the items where the value is null? e.g. special characters, value length is longer or shorter than a specific amount etc...

 Peter

In testing I have observed that if an appointment is created on the device this property is not populated, even when synchronised with Exchange. However if the appointment is created on the desktop the MeetingOrganizerName is filled in. I don't know if this explains any of your problem items, though it doesn't explain why you should get a value from the native POOM call and not from Mobile In The Hand.

Peter