Test/Debug Tools
Test/Debug Tools
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release. This topic provides information about how the different technologies compare with regard to Test/Debug Tools.
| Technology | What test and troubleshooting tools can I use? |
|---|---|
| Active Directory Services Interfaces (ADSI) | All standard test and debugging tools, as well as other Microsoft® and third-party test and debugging tools, can be used. |
| Collaboration Data Objects for Windows 2000 (CDOSYS) | No special debugging tools are needed to debug applications that use CDOSYS. |
| CDOSYS SMTP/NNTP Event Sinks | No special debugging tools are needed to debug applications that use CDOSYS. For particularly difficult protocol-interaction issues, a network monitoring utility may prove helpful, but is typically not required. |
| Collaboration Data Objects for Exchange 2000 Server (CDOEX) | No special debugging tools are needed to debug applications that use CDOEX. |
| Collaboration Data Objects for Exchange Management (CDOEXM) | No special debugging tools are needed to debug applications that use CDOEXM. |
| Collaboration Data Objects for Exchange Workflow (CDOWF) | No special debugging tools are needed to debug applications that use CDOWF. Custom applications might be created to analyze the process audit logs created during process execution. If you are using the Workflow Designer for Exchange 2000 Server, enable Just-In-Time (JIT) script debugging. JIT starts the Microsoft Script Debugger when the error occurs. The debugger starts on the server, so you need to have access to the server. |
| Exchange OLE DB Provider (ExOLEDB) | No special debugging tools are needed to debug applications that use ExOLEDB. |
| Exchange Store Event Sinks | No special debugging tools are needed to debug applications that use Exchange store event sinks. |
| Exchange Web Forms | No special debugging tools are needed to debug applications that use Exchange Web forms. Note, however, that because the forms execute on the computer running Microsoft Exchange Server 2003, debugging may require the developer have access to the Exchange server. Always use caution when allowing anyone direct access to the Exchange server. |
| HTTP/Web Distributed Authoring and Versioning (WebDAV) | No special debugging tools are required to debug applications that use WebDAV. For particularly difficult protocol-interaction issues, a network monitoring tool may prove helpful. The NETMON.EXE tool can be very useful in debugging WebDAV protocol interactions. Because WebDAV queries are sometimes sensitive to minor syntactical differences, a WebDAV query tool can also be helpful. |
| WebDAV Notifications | No special debugging tools are needed to debug applications that use WebDAV Notifications. For particularly difficult protocol-interaction issues, a network monitoring tool may prove helpful, but is typically not required. |
| Incremental Change Synchronization (ICS) | No special debugging tools are needed to debug applications that use ICS. |
| Lightweight Directory Access Protocol (LDAP) | No special debugging tools are needed to debug applications that use LDAP. For particularly difficult protocol-interaction issues, a network monitoring tool may prove helpful, but is typically not required. |
| Messaging Application Programming Interface (MAPI) | No special debugging tools are needed to debug applications that use MAPI. |
| Outlook Object Model (OOM) | No special debugging tools are needed to use OOM. |
| Outlook Web Access | No tools are available for debugging calls to Microsoft Outlook® Web Access, because the internal architecture is not available for debugging, and the URL calls required to access Outlook Web Access programmatically are not documented or supported. |
| Exchange Rules | No special debugging tools are needed to debug applications that use Exchange rules. Client-side rules require Outlook for proper testing. |
| SMTP Event Sinks | No special debugging tools are needed to debug applications that use SMTP event sinks. For particularly difficult protocol-interaction issues, a network monitoring tool may prove helpful, but is typically not required. |
| Windows Management Instrumentation (WMI) providers for Exchange | No special tools are required to debug applications that use WMI. |
| Exchange Backup and Restore API | No special tools are required to debug applications that use the Exchange Backup and Restore API. |
| Exchange writer for the Windows Volume Shadow Copy Service | No special tools are required to debug applications that use the Windows Volume Shadow Copy Service. |
Send us your feedback about the Microsoft Exchange Server 2003 SDK.
This topic last updated: June 2006
Build: June 2007 (2007.618.1)
© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.