In visual studio 2005 (using the Vista OS), I have an asp.net web project. When I debug, I have to manually attach to aspnet_wp.exe.

My project used to automatically attach to this process. How do I get it to automatically attach to it again?

Open the Web project's Properties pages dialog. Select the StartUp node. Make sure you have things configured correctly. My standard choices are a specific page, Use default Web Server and Debuggers - ASP.NET.

Thanks,

I did all that initially...same behavior...

I thought it might be project-specific so I brought up another application and the same thing is happening.

So apparently, I have turned off some debugging parameter inside Visual Studio.  Only I can't figure out where!

Hi Dexter,

From your description, I understand that the Visual Studio 2005 debugger can’t attach to the process automatically, you have to manually attach it. In addition, this issue occurs recently. If there has been any misunderstanding, please let me know.

In my opinion, I recommend you first run devenv /resetsettings in Visual Studio 2005 Command Prompt. This will reset the settings of Visual Studio 2005. If reset settings cannot fix this issue, please try to run devenv /setup, this method will initialize Visual Studio 2005.

Just a reminder, For the Operation System is Vista, please don’t forget to install Visual Studio 2005 SP1 and Visual Studio 2005 SP1 update for Vista.

Microsoft® Visual Studio® 2005 Team Suite Service Pack 1
http://www.microsoft.com/downloads/details.aspx?FamilyId=BB4A75AB-E2D4-4C96-B39D-37BAF6B5B1DC&displaylang=en

Visual Studio 2005 Service Pack 1 Update for Windows Vista
http://www.microsoft.com/downloads/details.aspx?FamilyID=90e2942d-3ad1-4873-a2ee-4acc0aace5b6&displaylang=en

I ran devenv /resetsettings.  However, I don't think it fixed my problem.  I happened to notice a message that flashed by in the Output window after I pressed F5 to try to start the debugger - :could not start debugger, script debugging has been disabled.  The message even told me where to change the option (Internet Explorer, Advanced tab).  I have no explanation for it but script debugging was turned off in Internet Explorer. 

So, I enabled script debugging in Internet Explorer but the debugger still does not automatically attach!  I then decided to run devenv /setup as you suggested.  But, I got the following error message:

The operation could not be completed. The requested operation requires elevation

I have no idea what that means so, I'm still stuck....

If you have any more suggestions, I would appreciate it.  In the meantime, I'll check for service packs as you suggested.

You account may not have debug priveledges. Has your network admins been changing your account access lately? Are you trying to debug against a local instance of IIS or the Development Web Server?

Ironically, this is my personal laptop....if I don't have debug privileges, I don't know what could have changed it.

I am using the Development Web Server?  How can I determine if my debug privileges were changed?

dexterm:

I then decided to run devenv /setup as you suggested.  But, I got the following error message:

The operation could not be completed. The requested operation requires elevation

Hi Dexter,

Have you tried to right click the shortcut (Visual Studio 2005 Command Prompt), and then select "Run as administrator"?

We recommend you to do the following when running Visual Studio 2005 on Vista.

    * Run Visual Studio with elevated administrator permissions
    * Be a member of the "Administrators" group on the local machine
    * Right-click the Visual Studio icon and select the "Run as administrator" option from the context menu

For your reference, please refer to the following link:

Visual Studio 2005 on Windows Vista Issue List
http://msdn2.microsoft.com/en-us/vstudio/aa964140.aspx

I ran devenv /setup with no apparent change.  However, on a whim I decided to load a WinForms project and I was able to use the debugger with it (i.e. the debug process was attached). 

So clearly, it has something to do with my Visual Studio settings on web projects (I have tried to different web projects and they both have the same problem).

I just don't what setting in Visual Studio controls whether to attach to a process or not when I press F5...

I am working on Visual Studio 2008.  I have this problem with both 2005 and 2008 on Vista.  I have no problems debugging, it is just that selecting Debug does automatically not attach to the process.  This is only the case for web projects, and not for Windows applications and other project types.

 I am running with elevated privileges.  Rarely and occasionally, VS will automatically attach.  When it does, it will continue to do so on successive debug commands, but eventually it stops attaching and it must be done manually.  Hitting debug does everything, builds, starts the development server, opens the page and simply fails to attach.

I am tending to think this is something that is somehow being blocked or lost, but it is not always consisitent.

It would be very helpful to have a resolution to this.  Most times I can get around it, but if I have a process that fires on application start or page load, it is very frustrating, as I'll have missed where I want to enter debugging.

Thanks,
John

This problem i got since installed new Internet Explorer 8. I can debug asp.net sites only if i closed all IE instances.