I have IIS 5.1 on a XP machine, and visual studio 2005. How do I go about attaching my debugger to IIS instance.
BTW: I'm not seeing the IIS process within the running processes or probably I don't know what to look for .
I have IIS 5.1 on a XP machine, and visual studio 2005. How do I go about attaching my debugger to IIS instance.
BTW: I'm not seeing the IIS process within the running processes or probably I don't know what to look for .
In Visual Studio:
Just to clarify Jimmie R. Houts answer…
If you want to debug the web application VS and IIS you can do the following:
Then in VS2005 do this:
Same works for VS 2008 also.
I'm running Windows 7 with IIS Version 7.5 and I also needed to tick the "Show processes from all users" and "Show processes in all sessions" boxes - at the bottom of the "Attach to Process" dialog.
Also I had put my app in a specific App Pool which means you can then see it labeled against the w3wp.exe.
The IIS process is aspnet_wp.exe.
In fact, attaching to the aspnet_wp.exe process is what VS does when you have your project set to use IIS for debugging.
You'll also need to open Internet Information Service From Control Panel > Administrative Tools. Right click the web site in question, click the home directory tab, and select the configuration button. This will open a new form with three tabs - click the debugging one and select the two options in the debugging flag section. This is also necessary to debug.
Using an Attach to IIS plugin (VS2015, VS2017) plugin saves a few clicks - especially when dealing with an ecosystem of IIS hosted sites (one frontend with multiple backend services say)