How To Break The MAPI Stub Library

Pre Vista Fix MAPI Download Still Available

SGriffin's MAPI Internals — Wed, 30 Jul 2008 17:37:07 GMT

Sorry for not posting this sooner - I just found out about it today. As I noted previously , we recently

Issues Loading ExMAPI32.dll Directly

SGriffin's MAPI Internals — Fri, 19 Sep 2008 16:28:36 GMT

In a previous article , I noted that you could load exmapi32.dll directly and bypass the MAPI Stub Library.

re: How To Break The MAPI Stub Library

Len — Wed, 26 Nov 2008 01:40:17 GMT

For third-party applications that explicitly loads MAPI32.dll, what's does Microsoft recommended on how to support both the mapi32.dll and exmapi32?

i.e

1. Should we compile two version of the application?

2. Use the stub mapi32 dll?

There was mention of a performance hit on using the stub mapi32.dll hence the Exchange server doesn't use the stub dll.

Are there documentation what the performance on using the mapi32?

In regards to the stub mapi dll, is the stub dll guarantee to be install on a new server?

Thanks.

re: How To Break The MAPI Stub Library

Stephen Griffin — Wed, 26 Nov 2008 03:38:52 GMT

If you're explicitly loading mapi, there's no reason to have two different binaries, as you can always decide what mapi to load on the fly. The Exchange MAPI download is built to use the stub library. If you want to bypass the stub and load exmapi32.dll directly, you can do that, but you'll want to wait for the fix I talk about in "Issues Loading ExMAPI32.dll Directly".

The stub library is an OS component. It comes with Windows. So it should be there on a new server.