Dmitry Streblechenko replied to Davide Angeli
22-Nov-09 10:29 AM

The way it used to work, mapi32.dll in the System32 folder got replaced.
Well behaved mail clients however leave mapi32.dll in System32 alone and
simply create a registry key that redirect calls to their dll that
implements Simple MAPI.
I very much doubt MS will break that. They might stop supporting Simple MAPi
in their own products (Windows Mail, Outlook, etc), but I do not see that
happening either.
--
Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool
-
Maybe I am a little bit confused, please help me : now in my software
I am loading mapi32.dll from 'windows\system32' folder and I suppose
that this is the Microsoft wrapper standard wrapper to simple MAPI for
the default mail client, is it wrong? For example if I am using
Thunderbird the real file is C:\Program Files\Mozilla Thunderbird
\mozMapi32_InUse.dll but I do not care where this file is because I
know that mapi32.dll in windows\system32 directory do the job for me.
My question is : in feature Windows versions, Microsoft will delete
windows\system32\mapi32.dll file and so it will be necessary to load
directly the client own version of the mapi32.dll?
Thanks