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

  • Live Event Date: December 11, 2014 @ 1:00 p.m. ET / 10:00 a.m. PT Market pressures to move more quickly and develop innovative applications are forcing organizations to rethink how they develop and release applications. The combination of public clouds and physical back-end infrastructures are a means to get applications out faster. However, these hybrid solutions complicate DevOps adoption, with application delivery pipelines that span across complex hybrid cloud and non-cloud environments. Check out this …

  • On-demand Event Event Date: October 29, 2014 It's well understood how critical version control is for code. However, its importance to DevOps isn't always recognized. The 2014 DevOps Survey of Practice shows that one of the key predictors of DevOps success is putting all production environment artifacts into version control. In this webcast, Gene Kim discusses these survey findings and shares woeful tales of artifact management gone wrong! Gene also shares examples of how high-performing DevOps …

Most Popular Programming Stories

More for Developers

RSS Feeds