Debugging an ISAPI extension

1. If IIS gets hosed, you can use VC++ to attach to the "inetinfo" to terminate it.

2. To stop the webserver you can use the following dos commandline

net stop "FTP Publishing Service" 
net stop "Gopher Publishing Service" 
net stop "World Wide Web Publishing Service" 

This saves you from starting the control panel and the services applet. You can add these commands to your Tools - menu.

3. To start again use
net start "World Wide Web Publishing Service" 

4. Also check out TN063: Debugging Internet Extension DLLs in the online help.



Comments

  • http://www.alrojo.com/html/videos-idx.htm

    Posted by Legacy on 06/11/2003 12:00am

    Originally posted by: Fermin

    Good work.

    Reply
  • net start is wrong

    Posted by Legacy on 03/22/2002 12:00am

    Originally posted by: Mike

    it should be 
    
    

    net start "World Wide Web Publishing"

    drop the service on each of the commands.

    Reply
  • Debugging ISAPI

    Posted by Legacy on 05/22/2001 12:00am

    Originally posted by: Ryan Permeh

    i've also found it veryuseful, epseccially in debug builds, to add a 
    
    __asm int 3

    as a breakpoint.

    this allows you to break a running process at a certain point and trace it there. useful for debug versions, but it will screw with you if you try to use it in a release version.

    Reply
Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Download the Information Governance Survey Benchmark Report to gain insights that can help you further establish business value in your Records and Information Management (RIM) program and across your entire organization. Discover how your peers in the industry are dealing with this evolving information lifecycle management environment and uncover key insights such as: 87% of organizations surveyed have a RIM program in place 8% measure compliance 64% cannot get employees to "let go" of information for …

  • Given today's threat environment and the increasing connectivity of digital infrastructures, security teams now realize that they must assume their IT environments are subject to periodic compromise. Gone are the days when preventive measures to secure the perimeter or trying to detect malware problems using signature-match technologies were enough. New practices based on an understanding of the phases of an attack, continuous threat monitoring, and rapid attack detection and remediation are necessary. This …

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds