What is the best way to get started using MAPI?

Question

I've been spending some time hacking away at MAPI for the purpose of creating tools for process automation on both server and client. Most of the resources I read online are either short on details and/or examples or full of conflicting information compared to other sources.

Assuming I have an understanding of C++, COM and .NET, what printed or online resources are best for getting started and contain a detailed reference?

Background: I'm working in an Exchange 2003 environment. We may go Exchange 2007 one day, but there's no push.

Answer 1

I thought MAPI was being phased out by MS themselves and that one should WebDAV as the preferred way of accessing info from Exchange? I'd encourage you to do the same...

Answer 2

We had a modest size Exchange 2007 project and had woes with it. We picked up WebDav first, then switched to MAPI and finally started using Web Services. While Web Services approach is definitely least ugly, it lacks flexibility and available commands (from my experience and point of view, of course).

For relatively simple scenarios I'd recommend using Web Services, if working with Exchange 2007. If you work with 2003 or earlier, choose between WebDav and MAPI.

Sorry for not actually answering your question, just throwing in my 2 cents.

HTH

Valve.

Answer 3

"Inside MAPI" is the best book on the topic. It's out of print, but you can still find it around. The best approach is probably to download MFCMapi from Microsoft with its source and look at how they do it.

Answer 4

Inside MAPI is surely the best book on this topic. You can buy the e-book on the website - if you prefer the dead tree edition, you will have to buy extraordinary expensive used copies on Amazon (I have actually done this).

As Outlook is built upon MAPI, it has proven to be the most stable technology to access Outlook and Exchange as Microsoft tends to introduce at least one new API with every Exchange version.

MAPI has been there, is there and will be there in the future.

Answer 5

We are doing a client side Outlook application along with a few services. MAPI seems to be the most durable API. I'm worried about the future, but it does seem that support will continue as OL is built on top of MAPI. However, the client libraries are shipped as a separate install. I'd also encourage you to look at Outlook Redemption. This has been a life saver for us: http://www.dimastr.com/redemption/