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

  • 10 Rules that Make or Break Enterprise App Development Projects In today's app-driven world, application development is a top priority. Even so, 68% of enterprise application delivery projects fail. Designing and building applications that pay for themselves and adapt to future needs is incredibly difficult. Executing one successful project is lucky, but making it a repeatable process and strategic advantage? That's where the money is. With help from our most experienced project leads and software engineers, …

  • As everyone scrambles to protect customers and consumers from the Heartbleed virus, there will be a variety of mitigating solutions offered up to address this pesky bug. There are a variety of points within the data path where solutions could be put into place to mitigate this (and similar) vulnerabilities and customers must choose the most strategic point in the network at which to deploy their selected mitigation. Read this white paper to learn the ins and outs of mitigating the risk of Heartbleed and the …

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds