You can now get the September 2007 release (126.96.36.1991) of MFCMAPI up on the Codeplex site: http://www.codeplex.com/MFCMAPI
I’m still getting the hang of Codeplex. There seems to be a lot of extra work involved in closing out bugs for a release. What I’m really looking for is a way to assign a list of bugs to a release, then in one operation mark them all as fixed and closed. But I can’t find a way to do that. Even doing the resolving manually seems to require extra steps: I have to first edit it to mark it fixed, commit that change, and then close it. Resolving a bug as fixed should be an atomic operation. (And as I re-read this paragraph to make sure it’s what I want to say, I discover the “Advanced View” of the Issue Tracker, which seems to be just what I want. Oh well – I’ll try it out on the next release!)
Anyway, here’s a list of what I fixed in this release:
- Crash on Vista during shutdown – Interesting lesson here in using LoadLibraryEx with the DONT_RESOLVE_DLL_REFERENCES flag. Might be worth a post of its own.
- Rules editing – A customer was asking about editing OOF rules with MFCMAPI, which led to the discovery that trying to ModifyTable with an empty PR_RULE_PROVIDER_DATA property is a bad idea. So now we check for and avoid that case.
- Table sorts – It doesn’t matter how many times you code review – cut and paste bugs still happen. In this case, my table sorting routine would never sort descending because I always passed TABLE_SORT_ASCEND.
BTW – would anyone be interested in a list of bugs fixed/features added between the MAPI Editor download and the initial Codeplex release? I put one together a while ago but never did anything with it. It’ll need some cleanup, but I could post it if there’s interest. I *may* even be able to track down what changed between the old KB article and the MAPI Editor download if there’s really strong interest. Let me know.