I launched Visual Web Developer Express 2008 last night, opened a web site I built last week and attempted to run the site. I got an error message along the lines of asp.net server is not working and the browser didn’t launch. After googling the problem and investigating a number of solutions I suspect the webdev.webserver.exe could be corrupted and some bloggers suggest that replacing this file could solve this such problem. I have found several locations which claim to provide downloads of webdev.webserver.exe but strangely none of them actually provide a link which downloads the file. For example is it just me or do the links on the following site just send you round in circles?..
Nightstalker, I am running Windows XP home so I don’t have IIS. I suppose I could reinstall VS but isn’t that a big solution to what could just be a small problem. I did get a prompt about .net 2.0 and .net 3.5 when I opened the site last night but foolishly I just clicked ok instead of reading it properly. I’m going to try posting this question on the web server forum. having done some googling I know I’m not the only person to have experienced this issue, if only I could find a reliable download for webdev.webserver.exe I could cross that solution off the list.
XP home. hmmm. That could be an issue on its own for web dev.
Have you installed all the version of the framework? Framework 2.0 and then 3.5? As 3.5 runs on top of 2.0. Sorry about the weird ideas, just shooting in the dark here.
My guess is that the problem is not with webdev.webserver.exe but with your site, or your machine setup if you “mess up” during the framework instalation.
Start debuging your site in visual studio with the option “step into instance” and set a break point in first line of application_start, or before the first line to execute.
Go to Debug > Exception , tick the Thrown checkbox for CLR exceptions.
I’ve run into stuff like this before… and I’ve seen many times the vs webserver crash at start up and was always a problem with a website application that blows up at start up or a when starting the server from the command line with wrong arguments (ex: missing virtual path argument), or even a page that get into a infinite loop.