Named Prop Name resolution for 3rd party properties.

Jan 15, 2010 at 8:14 PM
Edited Jan 15, 2010 at 8:14 PM


I noticed that most of the time the November 09 version of MFCMapi doent resolve all of the defined 3rd party named prop names on email objects.  I tested versions going back and found May 09 to be the last one that worked reliably. 

I since noticed it on other systems/environments where I've used this version on so I wasn't able to isolate it to something on that specific system.

Since July 09 appears to be the first version to have the issue, I checked your blog post on this version. Could there be a problem with the Named Properties optimizations that were put into place?



Jan 15, 2010 at 8:22 PM

You'll have to give more specifics about what you're seeing, especially the repro scenario. I can't think of anything in the named prop optimizations that would have any effect on 3rd party named props that wouldn't also affect MSFT named props.

Jan 25, 2010 at 12:46 PM

This is fixed in the January 2010 Release.