Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Nov 02, 2012 03:37 AM by Steammike
Oct 10, 2011 08:16 PM|LINK
I am using Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1, IIS EXPRESS 7.5
when I want to debug a page using dbgclr.exe, I am not able to find aspnet_wp.exe (or w3wp.exe) (they are not running).
What is the solution to this?
Oct 11, 2011 08:01 AM|LINK
I don't think they do, look for an iisexpress instance, it is that which will be serving your pages.
Oct 11, 2011 09:51 AM|LINK
Thanks for the reply.
I see 2 processes - 1. iisexpress.exe
But, when i try to attach to the iisexpress.exe process, I get an error message - "Unable to attach to the process. The debugger was unable to automatically select an appropriate type of code. Please manually specify the type(s) of code to which the debugger
Oct 11, 2011 10:58 AM|LINK
Have you tried, native code and script?
Oct 11, 2011 11:12 AM|LINK
How do I select these options?
Oct 11, 2011 03:14 PM|LINK
In type of process, I am getting - TSQL/x86 for iisexpress
Oct 11, 2011 07:48 PM|LINK
I am also not getting "Managed Code" as the type for the iisexpress process.
Oct 12, 2011 08:17 AM|LINK
This article describes how to configure your ASP.NET application for debugging, how to attach to the ASP.NET worker process (Aspnet_wp.exe) with the Microsoft CLR Debugger, and how to debug the application：
Oct 12, 2011 11:52 AM|LINK
But, the ASP.Net worker process(Aspnet_wp.exe) is not running.
What is the problem here?
Oct 13, 2011 05:55 AM|LINK
The way an ASP.NET request is handled by IIS is quite different in IIS 6.0 when compared with 5.0. In 5.0, the ASP.NET worker process is handed off control by the
aspnet_isapi extension in IIS. The aspnet_isapi dll runs in the inetinfo.exe process in IIS and functions what is known as the
CLR host (a CLR host is the piece of unmanaged code which is responsible for loading the CLR into the memory). So
aspnet_isapi “hands over” the processing to the worker process named aspnet_wp.exe, where the request passes through a series of HttpModules and an HttpHandler.
But in IIS 6.0, there is a driver named http.sys which listens to all the incoming requests (aspnet_isapi.dll is not in the picture at this point). The moment an ASP.NET specific request comes in, this driver starts an IIS 6.0 worker process (which
is not related to ASP.NET at all) named w3wp.exe. This process now loads the
aspnet_isapi.dll (CLR host) and the request follows through a similar sequence of HttpModules and HttpHandlers.
So the important thing to note here is that w3wp.exe is not an ASP.NET worker process (unlike aspnet_wp.exe) but instead specific to IIS 6.0.
Conclusion: if you use IIS6.0 or later, you will view the w3wp.exe rather than aspnet_wp.exe.