Visual Studio 2003 'debug processes' fails to see NET running in the IIS worker process (w3wp)

Usually, to debug my .NET dll, I typically just run my web application
until the DLL in question is invoked - at which point I can just
attach to it via Visual Studio .Net, and debug it. Two weeks ago I ran
into a problem where Visual Studio would fail to recognize that the
NET code is even associated to the IIS process - w3wp.exe. I have
checked with Process Explorer, and the .NET DLL is correctly
associated to the w3wp process - yet Visual Studio still fails to
recognize this fact. It sees w3wp, but only shows 'Win32' in the Type
column.

I have managed to reproduce this rather strange behavior on two
seperate machines, both running Windows 2003, and VS.net 2003. Both
systems were previously always used for development - I'm a little
puzzled as to why this started happening all of a sudden. I was away
from that code for a few months, so I'm thinking maybe this could be
the doing of a Microsoft update. Yet, on the second machine, it was
originally working (today - it actually saw NET running in w3wp) - and
without updating or anything, I rebuilt a few of my projects and the
next time I tried to debug, it didn't see .NET. In fact, on the second
machine, it hasn't recognized NET running in that process since that
time.

Has anyone else seen this behavior before? I don't necessarily NEED to
debug, but it would certainly make my job a little easier to have it
work again.

Any help is appreciated.
.

Relevant Pages

  • Re: debugging in asp.net and asp - urgent
    ... Are you receiving an instantiation error? ... I don't think you can debug into a .NET DLL even if you instantiate it ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Debug VS2005 .Net dll called from a VB6 exe
    ... Well if you only want to step in the error that occurs in the .Net dll then ... the VB6 debug build isn`t even necesary ... VB6 exe before i can attach to this process that then calls the .Net ...
    (microsoft.public.dotnet.general)
  • Re: Problem with Registering filter on windows mobile
    ... The fix is to modify C/C++ preprocessor definitions in the ... unresolved external because it's only defined in debug builds, ... the project using the visual studio wizard it worked, ... Windows CE Multimedia and Graphics ...
    (microsoft.public.windowsce.app.development)
  • RE: debugger doesnt stop at breakpoint while debugging SQLCLR functio
    ... It seems remote debugging component was not installed during Visual Studio ... I click Step into Function and I am able to debug the function step by step. ... Stored Procedure is in separate assembly which is created in SQL Server ...
    (microsoft.public.vsnet.debugging)
  • Re: Running and debugging a website on http://www.mysite.com instead of http://localhost
    ... I'm using Visual Studio 2003 Professional. ... Either way the obvious question would be whether or not you have debug ... enabled on what Visual Studio recognizes as a remote website. ... public static string ErrorUrl ...
    (microsoft.public.dotnet.framework.aspnet)