0

To start with, I blamed the slow startup on this problem:

VS2010 and IE10 Attaching the Script debugger to process iexplore.exe failed

But after I fixed that, it still takes a really long time to start up a new debugging session... long enough to make you want to skip debugging.. that's not acceptable.

It's so long I feel like something is timing out before it actually starts IE and brings up the page.

Does anyone have any idea why and how to fix it?

It happening in vs2010 and vs2012..

Thanks,

Eric-

Community
  • 1
  • 1
Eric Brown - Cal
  • 14,135
  • 12
  • 58
  • 97

1 Answers1

0

I often have this problem, usually after a couple of times of debugging, it turns to very slow to start up again.

What I do is to open task manager and kill the alive Webdev.Webserver40.EXE process which is not supposed to be there after you stop a debug.

diwatu
  • 5,641
  • 5
  • 38
  • 61