I'm using VS2010 Express with SP1 on XP Pro SP3. I have a web development site on a local drive that was running fine under IIS Express a few days ago. Now when I launch under IIS Express, IIS Express goes up to 50% CPU usage and doesn't come down, eventually freezing the machine for at least several minutes (at which point I do a hard PC restart). The site works fine under the VS Development Server (Cassini) and IIS 5.1.
Under IIS Express the page call is (the port number changes with each test site).
http://localhost:4306/mypage
The TraceError for one such hang event is here:
https://www.yousendit.com/download/UW13UGhTSWVwaFRvS3NUQw
I made two changes recently that might have affected things. 1) I made a copy of the site for operations testing and got it to run under IIS 5.1. Then I pointed IIS 5.1 at the development site, and got it to run; works fine. 2) I renamed the folder that the development site was in, and then could not figure out how to get VS2010 Express to recognize it on the start page; but I got past that.
I tried uninstalling IIS Express and reinstalling, no joy. Did that twice with a restart between uninstall and reinstall the second time.
I built a fresh new bare-bones web site using VS2010 Express in a different sub-folder of the development site parent folder and got the same result. I built a second new bare-bones web site using VS 2010 in a different unrelated folder (same drive) and it persistenty gave a "cannot display web page" error.
>> When I copied the main dev site pages etc. to a new "empty" web site on an urelated folder it gives the hang.
I just repeated the entire cycle of:
> new web site, run in IIS Express => ("cannot display page")
> reopen page in VS Development Server => works fine
>reopen again in IIS Express, => cannot display
>access through IIS 5.1 => works fine
>reopen again in IIS Express, => cannot display
Thes IIS Express address for the cannot display = http://localhost:3053/Default.aspx
A sample TraceLog for the cannot display situation above is at:
https://www.yousendit.com/download/UW13UGhha0RvQUo4SjhUQw
I tried looking at the IISExpress folder config files xml however it looks like a major learning curve which I'm hoping to shortcut with these posts.
I really need IIS Express because I've got extensive javascript and really don't want to go back to Cassini for JS debug.
I'm Ok about relocating the site elements to a new folder on the same drive, but would prefer the flexibility of not having constraints on where I put the dev site elements.
Any suggestions on how to get IIS Express back up and running properly on my development site would be appreciated.
Thanks!
====================
Update
It was pointed out that the above log file had a "attempt to attach an auto-named database" error, so I modified the web.config and I may have I eliminated that, but I can't be sure because I can't get another TraceLog with the "hang"; the system apparently hangs before generating the TraceLog.
Then I ran some more tests, below, in which I changed site start page. This initially generated a "cannot display page" error instead of the hang, so I thought the error might be more page specific. But then it generated the hang error on both of the target
pages, so that the "cannot display page" versus the hang is not consistent.
> Changed a connection string in web.config => it had two for the CTLS.mdb, a) one with a folder path, b) another with [DataDirectory]; removed b)
> Ran under VS Development Server => Worked
> Closed VS2010 Express
> Restarted VS2010 Express
> Ran Debug for site under IIS Express => instead of hang, gave "IE cannot display page"
> Repeated Debug for site under IIS Express => again, "cannot display page"
> In VS2010 Express, changed the start page to "SiteEntrance.aspx", repeated Debug under IIS Express => IIS Express hangs
> Rebooted PC
> Restarted VS2010, changed start page to "zTestLaunch.aspx", run Debug under IIS Express => "IE cannot display page"
> In VS2010 Express, changed the start page to "SiteEntrance.aspx", repeated Debug under IIS Express => "IE cannot display page"
> Stopped debug, restarted debug => cannot display page
> Stopped debug, restarted debug => cannot display page
> Closed VS2010 Express, noted it's pointing to IIS Express, restarted debug => cannot display page (page = SiteEntrance.aspx)
> Restarted VS2010, changed start page to "zTestLaunch.aspx", run Debug under IIS Express => IIS Express hangs
here's the TraceLog from one of the "cannot display page" events
https://www.yousendit.com/download/UW16aXRJNHY4Q1RvS3NUQw
Update:
Well, this problem is apparently so peculiar that nobody has heard of it or has any suggestions about it in four forums and one paid service. Next stop $259 at Microsoft support. EXCEPT - dumb me, I discovered don't NEED IIS Express to debug javascript in VS Studio Express( (which I thought I did - some misperception probably confused IIS Express with IE, which you do need) so, that being my driver, I don't need to work on this any further.
Finito! Thanks to anyone who read this far.
