![](http://support.microsoft.com/library/images/support/1ptrans.gif)
![](http://support.microsoft.com/library/images/support/1ptrans.gif)
![](http://support.microsoft.com/library/images/support/1ptrans.gif)
HOWTO: Debug ISAPI DLLs Under IIS 4.0 and IIS 5.0 (Q183480)The information in this article applies to:
SUMMARYDebugging of ISAPI Extensions and Filters under Internet Information Server (IIS) 4.0 is fully explained in the Microsoft Developer Network (MSDN) documentation. This documentation can be found in the following location: Platform SDK Web Services Internet Information Services SDK Programmer's Guide Developing ISAPI Extension and Filters Debugging ISAPI Extensions and FiltersPlease be aware that this documentation is not installed by the default installation option of NTOP or by adding IIS 5.0 to Windows 2000. However, it is available at the following link: MSDN Online MORE INFORMATIONFollowing are the steps for one method to debug an ISAPI Extension or Filter DLL. (It is assumed that Visual C++ is installed on the IIS computer.)
#define _WIN32_WINNT 0x0400 #ifdef _DEBUG char szMessage [256]; wsprintf (szMessage, "Please attach a debbuger to the process 0x%X (%s) and click OK", GetCurrentProcessId(), argv[0]); MessageBox(NULL, szMessage, "ISAPI/Filter Debug Time!", MB_OK|MB_SERVICE_NOTIFICATION); #endif Also, please note that medium Application Protection is a default setting of the IIS 5.0. NOTE 2 : For debugging purposes it may be either to configure IIS 5.0 application to run with low Application Protection. This will allow attaching debugger directly to inetinfo.exe process. REFERENCESWindows NT 4.0 Options Pack online documentation
|