Best IT Recipes

Attach a debugger to an IIS instance

I have IIS 5.1 on a computer with XP and visual studio 2005. How do I link my debugger to an IIS instance.

By the way: I don’t see the IIS process in running processes or probably don’t know what to look for.

+70
debugging c # visual-studio-2005
May 11 '09 at 16:46
source share
7 answers

In Visual Studio:

  • Click "Debug" in the menu bar
  • Click Join Process
  • Check " Show processes from all users " in the lower left corner
  • Select aspnet_wp.exe , w3p.exe or w3wp.exe from the list of processes
  • Click "Attach"
+113
May 11 '09 at 16:50
source share

Just to clarify Jimmy R. Houts's answer ...

If you want to debug the VS and IIS web application, you can do the following:

  • Site node inside IIS (virtual directory, etc.).

  • Then in VS2005 do the following:

    • Right-click on the web project → Properties → Launch Settings → Use User Server → Base URL → Enter the website address as Hosting in IIS.
    • Press F5 and you can debug your code

The same thing works for VS 2008.

+15
Apr 16 '10 at 9:04 on
source share

I am running Windows 7 with IIS version 7.5, and I also need to check the box "Show processes from all users" and "Show processes in all sessions" at the bottom of the "Attach to process" dialog box.

I also placed my application in a specific application pool, which means that you can see it marked on w3wp.exe.

+12
Oct 17 '13 at 20:45
source share

The IIS process is aspnet_wp.exe.

In fact, binding to the aspnet_wp.exe process is what VS does when you have a project to use IIS for debugging.

+5
May 11 '09 at 16:49
source share

You also need to open the Internet Information Service from Control Panel> Administrative Tools. Right-click the corresponding website, click the Home Directory tab, and select the configuration button. This will open a new form with three tabs - click on debug and select two options in the debug flag section. It is also necessary for debugging.

+1
May 11 '09 at 18:45
source share

Using the "Join IIS" plugin ( VS2015 , VS2017 ) saves a few clicks, especially when working with the ecosystem of sites hosted on IIS (one interface with several server services)

0
Feb 20 '18 at 22:43
source share

Possible ASP.NET process names:

  • w3wp.exe is IIS 6.0 and later.
  • aspnet_wp.exe is an earlier version of IIS.
  • iisexpress.exe is IISExpress.
  • dotnet.exe is an ASP.NET Core.
  • inetinfo.exe - old ASP applications running in the process.

C find ASP.NET process name

0
Sep 02 '19 at 2:20
source share


More articles:


All Articles