HOWTO: Debugging a Transport Provider with Visual C++
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:
- Close all instances of Mapisp32.exe.
- Set a breakpoint within the code for the transport.
- 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.
- Press F5 (Debug-Go) to start the debugger.
- 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.
Additional query words:
Keywords : kbAPI kbEDK kbMsg kbMAPI100 MAPIIXP
Version : WINDOWS:1.0
Platform : WINDOWS
Issue type : kbhowto