ASP.NET Development Server Hangs

ASP.NET Projects Take Forever To Load in Internet Explorer

If I hit F5 or CTRL-F5 in an ASP.NET project of Visual Studio, Internet Explorer would appear to hang. This problem would occur even in a new, 'empty' project with only one 'empty' default page.

I discovered a fix here but this post did not address the underlying root cause of the problem. Essentially,  the fix is to reset your Internet options in IE.

Tools > Internet Options > Advanced > Reset

internet_options

You get a message indicating the repercussions of your actions:

reset_settings

So before I reset the IE settings, I made a note of the 'current' settings so I could compare the changes afterwards. The results follow:

(Only changes are indicated and of course, your setting most likely are different than mine.)

Browsing Before After Resetting
Disable script debugging (Internet Explorer) UNCHECKED CHECKED
Disable script debugging (Other) UNCHECKED CHECKED
Reuse windows for launching shortcuts (when tabbed browsing is off) UNCHECKED CHECKED
Java (Sun)   Entire Node Removed
Use JRE 1.6.0_07 for <applet> (requires restart)   Entire Node Removed
Security    
Allow active content to run in files on My Computer* CHECKED UNCHECKED
Phishing Filter Turn on automatic website checking Turn off automatic website checking

Resetting did fix the problem, but I still don't know which one of these settings was the culprit.

I spent considerable time putting individual settings back to their original values, closing IE, and then running the same project, however the issue has not yet cropped up again.

Finally, I re-set all the values back to their original values thinking a combination of settings may have an affect. They didn't.

  • I didn't re-install Java, but I somehow doubt that's the culprit.
  • My cache and history had been emptied within the past one to two weeks.
  • I had not installed any toolbar components or addons.

 

This issue arose in the middle of... nothing. In other words, I'm working away, hitting CTRL-F5 many, many times during development and during the same development session the issue seems to have mysteriously popped up out of nowhere. No other applications of note were started.... no unusual disc or cpu activity.... just... nothing.

So while it appears the issue has been resolved, I'd still like to know exactly what caused it in the first place. If it happens again, I'll attempt to resolve the issue one step at a time, rather than hitting a single reset button and all its mysterious 'global' consequences.

8/21/2008 | Comments (3) in .Net
Email