Unable to start program 'http://localhost/Default.aspx'. VS2010

Question

I cannot start my website from Visual Studio 2010 anymore.

For a few days I cannot start my project in a web browser using F5. When I open my web application directly by

Answer 1

Please set your page name e.g Default.aspx revert to parent in IIS configuration

Answer 2

the solutions for me is to test with 127.0.0.1 in place of localhost. and all goes well for.

so the problem come from the host resolution name, to solve it please proceed like :

• open cmd and then tape : %systemroot%\System32\drivers\etc\
• open hosts file with notepad and the look for localhost ligne(you'll find 0.0.0.0 befor it )
• change the 0.0.0.0 with 127.0.0.1 at all lignes with localhost .

Answer 3

I'm using VS2012 with an ASP.net app that was written using VS2003... I've tried everything to get the IE page to open automatically when I select F5, or even Ctrl+F5... Haven't been able to get anything to work... However, I have stumbled upon a very poor work-around. When I select debug and I get the 'Unable to start program...' msgbox... I noticed that on the icon-tray I get a msg saying local-host has started

You'll notice a picture that the msgbox is pointing to: Well, if you right click it, you get three options:

When you select the first: 'Open in Web Browser', it will open IE with the page your working with...

Like I said, it's a very poor work-around... but it works. This isn't an issue when I select debug using 'Chrome' or the page-inspector... But they have their own issues.

Answer 4

Change the View Browser to another browser. Run the view in browser or debug, then change back to original browser should work after that.

Answer 5

I had the same problem. When I debug my code it says:

Unable to start program 'C:\homework.exe'. this system cannot find the file specified."

I'm using Microsoft Visual C++ 2010 Express but when I made a new project by the following steps:

Open C++:

1. Press new project
2. Press win32
3. Press win32 Console Application
4. Rename it
5. Click next
   make sure: that the application type is console application
   additional options: empty project*
6. Press Ctrl+Shift+A
7. In Visual C++/Code section press C++ File (.cpp)
8. rename it and press add

It works fine with for me now.

Answer 6

I'll share my experience with this same problem. This is not a solution, but someone may be able to figure out the problem from my particular experience.

I've been having this same problem for a few weeks now. (I don't know what changed on my system.) I do not run as local admin, because we are not allowed to have admin privileges on our PCs where I work.

Until today, I could expect F5 (Start Debugging) to start up a new local VS web server, open an IE window, and then issue an "unable to start program http://localhost:nnnn/Login.aspx" and "access is denied" error pop-up. If I closed the IE window, waited a few seconds, and then clicked F5 again, it usually started up my web app in debug mode just fine from that point on.

But today, that all changed. I did not change any configuration on my web app, which has been running fine, but I did add a couple of more classes to one of my subprojects. At this point, I could never get past the "unable to start program" message. I could run my app without debugging, but that was rather pointless. I even tried attaching to a running (non-debug) IE process, but that did not work.

Finally, I modified some of the properties in the WebAppName >Web >Servers screen. Specifically, I enabled "Specific port" for a specific HTTP port (which VS had been using all along), and I disabled "NTLM Authentication". I also enabled "ASP.NET" in the Debuggers section. Some of these I first clicked, then unclicked, then clicked again, saving in between each click.

This time, running with debug (F5) worked.

After running several times, I still usually get a "unable to start" error the first time after a recompile, but I can still usually get a debuggable running app to start after the second or third try. At least I'm back to where I was yesterday.

I suspect it has do with VS reloading its execution profile, and also probably something to do with permissions (since I cannot run as admin).