I am using VS2010 Express with SP1 on XP Pro SP3. I have a local development web site that was running IIS Express a few days ago. Now, when I start up in IIS Express, IIS Express reaches up to 50% of the CPU usage and does not crash, eventually freezing the machine for at least a few minutes (after which I reboot the hard computer). The site works fine under VS Development Server (Cassini). In the IIS Express page call page
http:
TraceError for one such event:
https:
I recently made two changes that could affect things. 1) I made a copy of the site for testing operations and made it work under IIS 5.1. Then I pointed IIS 5.1 to the development site and got it to run; works great. 2) I renamed the folder in which the development site was located, and then I could not figure out how to make VS2010 Express recognize it on the start page; but I walked past this.
I tried uninstalling IIS Express and reinstalling it without joy.
I tried to look at the xvi configuration files of the IISExpress folder, but I can not find the documentation to tell me what I can do with them.
I built a new new site with bare bones, using V2010 Express in a different folder, and got the result.
I need IIS Express because I have extensive javascript and REALLY don't want to go back to Cassini for debugging JS.
Any suggestions on how to get IIS Express support and work correctly on my development site will be appreciated.
Thanks!
Update
It was pointed out that the error “attempting to bind database with auto-name” occurred in the above log file, so I changed the web.config file and maybe I fixed it, but I can’t be sure, because I can’t get another one TraceLog with a hang; the system apparently hangs before creating TraceLog.
Then I conducted a few more tests in which I changed the start page of the site. This initially generated a “don't display the page” error instead of a freeze, so I thought that the error might be more specific to the page. But then he generated a freeze error on both landing pages, so that “the page cannot be displayed” is not consistent with the freeze.
The connection string was changed in web.config => she had two for CTLS.mdb, a) one with the outline of the folder, b) the other with [DataDirectory]; removed b) Ran under VS Development Server => Closed VS2010 Express worked; Restarted VS2010 Express Ran Debug for a site under IIS Express => instead of freezing, gave "IE cannot display the page" Re-debugging for a site under IIS Express => again, "impossible display page "
In VS2010 Express, the start page was changed to "SiteEntrance.aspx", Debug repeated in IIS Express => IIS Express hangs Restarted PC Restarted VS2010, changed the start page to "zTestLaunch.aspx", Debug started in IIS Express => "IE cannot display page "In VS2010 Express changed the start page to" SiteEntrance.aspx ", repeated Debug in IIS Express =>" IE cannot display the page ", Stop debugging, restart debug => do not display the page Stop debugging, restart debug => do not display the page Closed VS2010 Express, noted that it points to IIS Express, restarted debug => cannot from Braz page (page = SiteEntrance.aspx) restarted VS2010, change the start page in the "zTestLaunch.aspx", launched under the Debug IIS Express => IIS Express hangs
here TraceLog from one of the events "cannot display the page"
https:
Update:
Well, this problem is apparently so unusual that no one has heard about it in four forums and one paid service. Next stop is $ 259 with support from Microsoft. EXCEPT - dumb me, I found that IIS Express DO NOT need to debug javascript in VS Studio Express ((which I thought I did), some misunderstandings probably confuse IIS Express with IE that you need), therefore, Being my driver, I don't need to work on this anymore.
Finito! Thanks to everyone who read this far.