If you want to do managed code development for Outlook/Exchange at a similar level to Extended MAPI you're out of luck at the moment. Perhaps you are tempted to write a managed wrapper for Extended MAPI. If so this MSDN newsgroup posting may give you pause for thought. Stephen Griffin from Microsoft warns against this in several posts to the thread, including:
That said - I must strongly encourage Sagui not to follow your advice concerning MAPI and CDO with .Net. I'm one of the guys these crashes and hangs come to for analysis when they get reported. We've had a number of Fortune 500 companies have critical line applications come to a dead halt because they chose to ignore us and develop a component of the application with MAPI or CDO and .Net. The problems ARE there when you start scaling up. If you haven't hit them yet, you've just been lucky.
Fortunately the situation should improve. I mentioned Exchange Web Services a couple of months ago and I've just had a look at the slides of the PDC presentation Office 12: Developing Solutions Using the Consolidated Outlook Object Model(PPT) The Outlook 12 Object Model is a set of enhancements to the existing Object Model and is fully supported for managed code developers. Some of the features that could be useful for me are:
- Much better performance for handling large collections in Folders and Search Folders.
- Access to MAPI Store/Folder properties not in Outlook OM.
- Enhanced event handling.
- Access to hidden messages.
It will be interesting to see if it supports everything you can do in Extended MAPI.