HOWTO: Debugging a Transport Provider with Visual C++

 Last reviewed: July 25, 1997
Article ID: Q168239
The information in this article applies to:
  • Extended Messaging Application Programming Interface (MAPI), version 1.0
  • Exchange Development Kit (EDK)

SUMMARY

When trying to write a transport provider using MAPI, it may become necessary to trace the code in the provider. The following article outlines the steps necessary to accomplish this.

MORE INFORMATION

The reason debugging a transport seems difficult is because MAPISP32 loads the transports. Most users try to associate the mail client as the executable to run. The following steps allow you to debug a transport and step through its code line by line:

  1. Close all instances of Mapisp32.exe.

  2. Set a breakpoint within the code for the transport.

  3. Go to the settings for the project and select the Debug Tab. On the Debug Property Page, type Mapisp32.exe for the Executable for debug session.

  4. Press F5 (Debug-Go) to start the debugger.

  5. Start the mail client and select the profile that uses the transport.

When the spooler invokes the transport, you should be able to step through your code. It is important to make sure Mapisp32.exe is not already running when the debug session is started. If Mapisp32.exe is already running, the client will use the already running spooler and your code will not be shown. 
Keywords          : EDKAPI EMAPI MAPIIXP
Version           : 1.0
Platform          : WINDOWS
Issue type        : kbhowto
Solution Type     : kbservicepack

================================================================================

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: July 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.