views:

254

answers:

3

I have a Silverlight project (with ASP.net MVC web project)

Suddenly, when I press F5 it takes like 20 seconds, from the moment that Internet explorer opens, to when the debugger is attached. Mind you, it is a project that works perfectly since about 3 months. The problem just started last days.

When I start without debugging, everything runs just fine.

Any pointers on how to solve this?

edit: When I look at the output window, all it does is loading all the different assemblies, but one at a time at a painfully slow pace...

Also note that other project seem to start normally, even when debugging.

A: 

I have seen random slowness as well when trying to run web applications using "F5". I think a lot of it is due to the client side debugging features in VS2008 which seem to take some time to load. Did you recently add any large javascript libraries to your project?

Most of us just start the web app without debugging then attach the debugger to the worker process if needed. Since most of the time we don't need the debugger functionality. If we need client-side debugging we use firebug or the IE dev toolbar.

Dan
+4  A: 

I had the same issue a few months ago I surfed around for hours, finding different solutions and finally the solution was really trivial - just click Debug -> Delete all breakpoints. For me it was weird, as I didn't have any breakpoints I knew of... but it worked... I had removed them by hand but after selecting Delete all breakpoints from the menu it started to work ok again...

Hope it helps... because this is the most annoying problem I have ever had with VS :)

texmex5
Eeeuh, without knowig your comment, I 'accidentally' deleted all the breakpoints. And looking back to your answer, it seems to work for now :)wtf :)
Tom Deleu
+1 for saving the day.
Karl
Yep, I used to have this issue then I realized that I had 25+ breakpoints in catch blocks. Deleted all but the ones I needed and it started working again. Found this bug 2 years ago. Apparently not fixed.
jcollum
in my case my project was really small and I had only a few break points (definitely less than 5) and the slowness began ... after I had removed the breakpoints I could again but back my 5 breakpoints with no problem or slowness... so it seems pretty random ...
texmex5
Same here as texmex5. I now have about the same amounts of breakpoints set again, but it still works. bu hey, i'm not complaining :)
Tom Deleu
perhaps someone should report this on MS's Connect?
Mitch Wheat
My first report on ms connect :) https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=401266
texmex5
A: 

I have seen a slowdown issue if (as many companies do) your My Documents directory is mapped to a network drive. Visual Studio stores several settings here which may slightly increase latency when debugging. Change this back to a local drive and you may see an improvement which may also extend to other apps.

arch