PC MAPI: How to Resolve MAPI Name Mangling in Visual C++

Last reviewed: September 16, 1997
Article ID: Q134203
3.00 3.20 MS-DOS kbtool

The information in this article applies to:

  • Microsoft Mail for PC Networks, versions 3.0 and 3.2

*****************************************************************

**                          - WARNING -                        **
**    THE INFORMATION BELOW IS PRELIMINARY AND HAS NOT BEEN    **
**    CONFIRMED, EDITED OR TESTED BY MICROSOFT.  USE ONLY      **
**    WITH DISCRETION.                                         **
*****************************************************************

SUMMARY

With versions 3.0 and 3.2 of Microsoft Mail for PC Networks, programmers may create their own Windows interfaces to the postoffice using the Simple Messaging Applications Programmer's Interface (MAPI). With Microsoft Visual C++ version 1.5, 2.0, or 2.1, programmers may run into the typical "name mangling" problem during the link process that affects C++ programs linking DLLs created by a C compiler.

MORE INFORMATION

Programmers may solve this "name mangling" problem by changing the way the MAPI.H header file is included in the Visual C++ program. Instead of the standard include:

   #include "mapi.h"

Programmers should use the following:

   extern "C" {
   #include "mapi.h"
   }

Using the "extern" keyword in such a manner tells the Visual C++ compiler to link the MAPI.DLL library correctly and resolves problems with "name mangling".


Additional reference words: 3.00 3.20 smapi
KBCategory: kbtool
KBSubcategory: MailPCMAPI


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 16, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.