All geek questions in one place

Stopping web application debugging on IIS in VS2010 takes a lot of time

Whenever I stop debugging an ASP.NET IIS web application, it seems like it will take a very long time before VS2010 becomes responsive again (2 or 3 minutes). This happens when I close Internet Explorer 9 (which stops the debugging session), stops debugging in VS (which closes the browser) or when I disconnect the debugger from the debug menu (which leaves the browser open).

My CPU time for devenv.exe increases during this period to 25%. I am using a professional edition (without intellitrace). Starting without debugging is fine when I close the browser. I have add-ons and extensions installed as TestDriven.NET, Resharper, PowerCommands, Powerpower Tools, VisualSVN, ...

Any ideas what causes this nasty problem? What can I try and disable?

+3
source share
2 answers

You need to narrow it down by running Visual Studio in safe mode . This will disable all third-party extensions.

If the problem goes away, the problem is in one of your extensions. Try turning them on one at a time.

If the problem persists, then this is a problem with VS2010. Change the error in Connect. Also, try the preliminary release of VS2010 SP1 to make sure it is already fixed.

+3
source

Have you tried to kill the tray icon (asp.net web server) near the clock? Typically, a web server causes Visual Studio to freeze.

0
source

Source: https://habr.com/ru/post/1783216/

More articles:


All Articles