Visual Studio 2012 now very slow when starting to debug a website

I'm working on a .NET 4 website which accesses a sql server database, using Visual Studio 2012 Pro (version 11.0.51106.1 Q11REL)

When I hit "Start Debugging", it launches IE9 (blank), then loads symbols, then displays the specific page in the start action.

Suddenly last week, I went from seeing my page in about 5 seconds to 30-60 seconds!
I didn't change anything significant on my machine (I don't think; maybe I installed Update 1 to VS 2012?).
Update: it's not Update 1. I uninstalled and reinstalled from DVD, and it's still super slow. I even defragged the hard drive before reinstalling.

More specifically, I see the "loading symbols for..." messages, in VS' status bar, at a rate of about 1-2 per second, which is absurd.

Any ideas?

notes:
- this is on a fast laptop (i5, lots of memory, lots of free hard disk space, low CPU utilization)
- the project is set to use VS Development Server and only debug ASP.NET (Edit and Continue is disabled)
- it doesn't matter if I access my local copy or a remote copy of the database
povjetsetAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
povjetsetConnect With a Mentor Author Commented:
Problem solved: delete all breakpoints
Worked like a charm, now my page comes up in under 1 second!

Apparently if you have a breakpoint set on a function or dll that no longer exists, VS will do a lot of scanning.

Found this via roopeshreddy's Microsoft Connect link:
http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/98f50717-c842-4bb1-8676-f64d453f80d1

(I guess I didn't have quite the right search terms in google the first time around)
0
 
Roopesh ReddyIT AnalystCommented:
Hi,

Try the solution as suggested in this thread - http://stackoverflow.com/questions/12567984/visual-studio-debugging-loading-very-slow

Hope it helps u...
0
 
povjetsetAuthor Commented:
Thanks, but I had already seen that thread and those suggestions didn't help (including the more recent posts in that thread).

Also, fyi, if I do "Start without debugging" my website does come up within 2 seconds.
Currently it's a consistent 30 seconds to "Start with debugging"

It used to be fast when debugging, and on a co-worker's machine, the exact same project in VS 2012 does come up quickly in the debugger (5-10 seconds). We've compared a bunch of settings too.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
Roopesh ReddyIT AnalystCommented:
Hi,

Did you tried installing any updated? I mean Windows Operating System updates?

If not, try it!

Hope it helps u...
0
 
povjetsetAuthor Commented:
Everything is up to date via Windows Update
0
 
Roopesh ReddyConnect With a Mentor IT AnalystCommented:
Hi,

Weird!!!

Mean while, try to post the query in Microsoft Connect - https://connect.microsoft.com/VisualStudio

where Microsoft tech guys will be looking at the issue!

Moreover, you can try clearing the Cache - http://www.symantec.com/connect/downloads/clearing-temp-locations-and-aspnet-cache-system

Hope it helps u...
0
 
povjetsetAuthor Commented:
While roopeshreddy pointed me to a good site to post a question, he didn't point me to the relevant article that already answered it
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.