Repointing localhost after upgrading VS2003 project to VS2005

Question

1.00/5 (1 vote)

See more:

VS.NET2003

, +

I’ve been a VB.net Winforms developer the past few years and I now have a need to work on my 1st Web app. A couple of years ago I took a series of 1 day courses on ASP.Net but until now I haven’t had a chance to put that knowledge to work. I’ve been tasked to upgrade/rewrite an existing VS2003 Web project. The person that wrote it no longer works for our company but I do have the source code. I only have VS2005 so I have been trying to upgrade the app to that version and I’m having some issues. When I open up the Solution in VS2005, it brings up the upgrade wizard. When it finishes, it says it has upgraded the solution but it gives me an error saying: Unable to open the Web 'http://localhost/MyApp'. Could not find a Web server at 'localhost' on port 80. How do I fix this so it points to the right web server? Also, since I am new to web apps, I am wondering if someone could point me to a few good ASP.Net tutorials so I can brush up on things a bit before hitting this project. Any help in this area would be appreciated.

Posted 24-Apr-13 8:46am

theskiguy

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2013-04-24T10:42:00

It's hard to see where did you screw up this without seeing all your steps. Usually, running a valid ASP.NET application presents no problems.

I would advise the following: create a simple Web site from scratch. The URI http://localhost is used for testing/debugging on an development computer under the HTTP server bundled with Visual Studio. When you do everything from scratch and hit "Run" for the very first time, this "development HTTP server" is started. You will get a window where you can choose a URI to load first, one of those available in your project. When you do the basic exercises, you might be able to see how to revive your legacy project. If you wish, you can run any other HTTP server, but it won't let you debug your server-side code and it has to support ASP.NET.

[EDIT]

My other advice: from your legacy project, remove everything which is not a pure source code. Build and start it from scratch. Naturally, you should clear understand what is source code and what's not, no matter what work do you do. Remove all "obj", "bin", "*.user", "*.ncb"… Sometimes, project clear operations (from project menu or Solution Explorer) helps, but cleaning it manually before even starting Visual Studio is the most sure method.

[END EDIT]

Learning ASP.NET? I think there is nothing better than starting from http://www.asp.net/get-started[^].

Good luck,

—SA