M
Martin Odhelius
Hello,
I have a very fustrating problems while debugging ASP.NET applications.
When I am debugging and stepping thru code (with F10 or F11) Visual
Studio some times suddenly just stop responding and the only way get it
up and running again is to kill the aspnet_wp.exe process. When the
debugger hangs there is almost no CPU load, so it doesn't seem to be any
hidden eternal loop or anything like that. I have tried to reinstall IIS
and .NET Framework, and before that I have also run aspnet_regiis
several times but without luck. The code is compiled for .NET 1.1 and
the Web Site is configured to run under framework v1.1.4322. This
behaviour happens in several different projects, so it is not bound to
any specific code. I have just choosen to debug CLR-code. I have no
active watches that is slowing down the debugging. I've also tried to
debug in both VS2003 as well as in VS2005 (by attaching to the
aspnet_wp.exe process) but I get the same result, even if it semms to
happen much less often in VS2005. And btw, I have no antivirus programs
installed. I'm going crazy on this, please help!
Best Regards
Martin
I have a very fustrating problems while debugging ASP.NET applications.
When I am debugging and stepping thru code (with F10 or F11) Visual
Studio some times suddenly just stop responding and the only way get it
up and running again is to kill the aspnet_wp.exe process. When the
debugger hangs there is almost no CPU load, so it doesn't seem to be any
hidden eternal loop or anything like that. I have tried to reinstall IIS
and .NET Framework, and before that I have also run aspnet_regiis
several times but without luck. The code is compiled for .NET 1.1 and
the Web Site is configured to run under framework v1.1.4322. This
behaviour happens in several different projects, so it is not bound to
any specific code. I have just choosen to debug CLR-code. I have no
active watches that is slowing down the debugging. I've also tried to
debug in both VS2003 as well as in VS2005 (by attaching to the
aspnet_wp.exe process) but I get the same result, even if it semms to
happen much less often in VS2005. And btw, I have no antivirus programs
installed. I'm going crazy on this, please help!
Best Regards
Martin