The November 2009 Release (build 6.0.0.1016) is live: http://mfcmapi.codeplex.com.
The September 2009 release was downloaded over 18 thousand times, with nearly 1700 of them being the 64 bit build. This exceeded the July build by about 4000 downloads. Yay MFCMAPI!
Mostly bug fixes this time around. Win 7 finally made me dig into why Close All Windows wasn’t working, and I did a bit of work to make MFCMAPI a better multimon client.
Here's a change list - see the Issue Tracker on Codeplex for more details, or look at the code:
Enjoy.
I saw a note from somebody posted somewhere about GetMailboxTable not working against Exchange 2010. I don't think there was any conclusive answer to it.
I was wondering if you had any idea why it would not work. In particular, using the MFCMAPI Get Mailbox Table menu works fine against our Exchange 2007 and 2003 servers, but not against Exchange 2010.
The error dialog shows MAPI_E_CALL_FAILED at line 660 in MFCUtilityFunctions.cpp.
Many thanks.
RE Exchange 2010: Wait for an update to the MAPI download some time in December to fix these issues.
While applying a restriction RES_SUBRESTRICTION the Sub Restriction editor window has incorrect hex value for "0x0E120102 PR_MESSAGE_RECIPIENTS
0x0E130102 PR_MESSAGE_ATTACHMENT" 0x0E130102 represents PT_BINARY shouldn't it be 0x0E12000D i.e. PT_OBJECT?
The GetMailboxTable problem is fixed with the Mapi download 6.5.8147.
Have you seen an issue with MFCMAPI (running with OutLook 2010 MAPI environment) crashing when opening an Ex2010 Online Archive store?
I can double click on the store and get the window with the expandable tree into the store but then when I click on the '+' to view it, the crash occurs.
As far as I know there is nothing special about our Ex2010 installation or OutLook client installation.
In particular, it throws an unhandled exception (Access violation reading location 0x00000022) in mapiFunctions.cpp::GetPropsNULL on the call to:
WC_H(lpMAPIProp->GetProps(
lpTags,
ulFlags,
lpcValues,
lppPropArray));
lpTags has 0x3a cValues
Thank you.
I think this is a bug in Outlook's MAPI that should be fixed by RTM.