Debugging Problems

[josef]

I am having trouble debugging with Visual Studio.NET 2003 and Framework
1.1. I cannot press F5 and have the web project start with the
debugger, I get "Unable to start debugging on the web server. Could not
start ASP.NET or ATL Server debugging". So, instead I have to manually
attach to aspnet_wp.exe. This works about 50% of the time, the other
50% I have to restart IIS and/or manaully kill the aspnet_wp.exe
process, then manually attach the debugger to aspnet_wp.exe. I can
successfully debug Windows Applications with F5.

One thing I've noticed is I can't use localhost as the webserver, I
instead have to specify the machine name as well as having to setup a
header in IIS using the machine name. VS.NET now thinks I am
debugging/developing against a remote server.

I am stumped, though my frustration level is less than yesterday. I've
done all the typical things I know, ASPNET in the Debuggers group, set
Directory Security to my account which had administrative rights. But
this time it doesn't look like a security issue.

Any thoughts?

[Yunus Emre ALPÖZEN [MCSD.NET]]

What does %windir%\system32\drivers\etc\hosts file shows about your computer
localhost should be mapped rollback address (127.0.0.1)

--

Thanks,
Yunus Emre ALPÖZEN
BSc, MCSD.NET

<jo***@wainz.net> wrote in message
news:11********************@g43g2000cwa.googlegrou ps.com...

I am having trouble debugging with Visual Studio.NET 2003 and Framework
1.1. I cannot press F5 and have the web project start with the
debugger, I get "Unable to start debugging on the web server. Could not
start ASP.NET or ATL Server debugging". So, instead I have to manually
attach to aspnet_wp.exe. This works about 50% of the time, the other
50% I have to restart IIS and/or manaully kill the aspnet_wp.exe
process, then manually attach the debugger to aspnet_wp.exe. I can
successfully debug Windows Applications with F5.

One thing I've noticed is I can't use localhost as the webserver, I
instead have to specify the machine name as well as having to setup a
header in IIS using the machine name. VS.NET now thinks I am
debugging/developing against a remote server.

I am stumped, though my frustration level is less than yesterday. I've
done all the typical things I know, ASPNET in the Debuggers group, set
Directory Security to my account which had administrative rights. But
this time it doesn't look like a security issue.

Any thoughts?

[josef]

I've added entries to the hosts file for localhost and my computer
name; both mapped to 127.0.0.1. Complete reboot and still the same
error.

Any more thoughts?