Quantcast
Channel: Internet Explorer Web Development forum
Viewing all articles
Browse latest Browse all 3527

IE8 bug: unable to auto attach debugger in Visual Studio 2003 using IE8

$
0
0

When starts debug in Visual Studio 2003, it starts with a successful attachment to aspnet_wp.exe:

Auto-attach to process '[384] aspnet_wp.exe' on machine 'ITDEV' succeeded.
'DefaultDomain': Loaded 'c:\windows\microsoft.net\framework\v1.1.4322\mscorlib.dll', No symbols loaded.
....
But it ends up with:

The program '[384] aspnet_wp.exe: /LM/w3svc/1/root/...' has exited with code 0 (0x0).
The program '[384] aspnet_wp.exe: DefaultDomain' has exited with code 0 (0x0).

and Visual Studio returns to [Design] mode after hitting the first breakpoint.

Several people have complained about this problem on the internet without an answer.

I had tried fixes in Visual Studio, IIS, and IE without a luck. I suspected this is a bug in IE8. After uninstalling IE8, I have tried both IE6 and IE7. Both browsers work normally for debugging.

-----------

Reply to Sheng:

Thanks. This is more of an IE problem. I just wanna report this to Microsoft and make this issue easier to be searched out. I have just found out there are solutions suggested by some people online:

http://stackoverflow.com/questions/663144/why-cant-i-debug-from-visual-studio-2005-after-installing-ie8
 


Viewing all articles
Browse latest Browse all 3527

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>