I'm running Windows Server 2003, IIS 6.0, and VS 2003. I have an
ASP.NET project I previously created, and went to open it back up to
make modifications. Now VS won't open http://localhost
When I try to open that location, it just goes to "My Documents"
I haven't changed anything on the machine, I made sure the VS users
group had full access to wwwroot. I ran aspnet_regiis -i to reinstall.
I tried substituting my IP address for localhost. Nothing has worked.
Help! I need to recompile some small changes in this app and the entire
team is breathing down my neck wondering why I can't open up code on
the box I terminal server into.
And believe me, some on this team have really bad breath! :(
Help!
Peter van der Goes - 24 Feb 2005 15:00 GMT
> I'm running Windows Server 2003, IIS 6.0, and VS 2003. I have an
> ASP.NET project I previously created, and went to open it back up to
[quoted text clipped - 13 lines]
>
> Help!
Is the project in question on your local hard drive? I'm assuming it is as
you are trying to access http:\\localhost.
Have you tried the following:
(I assume that you've verified that your IIS is up and running properly)
Navigate to the project folder under InetPub\wwwroot.
Double-click on the project or solution file in the project folder.
Exactly what error message do you get if this doesn't work?

Signature
Peter [MVP Visual Developer]
Jack of all trades, master of none.
IT Drone - 24 Feb 2005 21:23 GMT
I get:
The web server reported the following error when attempting to create
or open the Web projet located at the following URL:
'http://Localhost:/Inbound'. 'A connection with the server could not be
established.'
Now looking at this what's weird is the colon after localhost.
But even if I just say "Open Project From the Web" and specify
http://localhost it fails and opens a window on My Documents instead.
IT Drone - 24 Feb 2005 23:34 GMT
One other thing. I created a new virtual directory and tried running
the BizTalk web services publishing wizard to publish the
orchestration, and that failed as well. I'm running all of this under
an admin account, so I don't think it's a privileges issue. One day it
was all working fine, the next, poof! And I'm the only one using this
server, so I know nobody else messed it up.
IT Drone - 25 Feb 2005 01:11 GMT
Well, I solved it. In case anyone else has the same problem, the
solution was to turn on the telnet service. Why in the world this
worked, I have no idea, since I would think that telnet was disabled
all along. But perhaps some service patch got applied that flipped it
from automatic to disabled.
In any event, I enable telnet, and it all magically works.
Peter van der Goes - 25 Feb 2005 13:03 GMT
> Well, I solved it. In case anyone else has the same problem, the
> solution was to turn on the telnet service. Why in the world this
[quoted text clipped - 3 lines]
>
> In any event, I enable telnet, and it all magically works.
I'm glad you got it sorted. I would not have come up with that.
Thanks very much for posting your solution!

Signature
Peter [MVP Visual Developer]
Jack of all trades, master of none.
Kyle Alons - 25 Feb 2005 13:40 GMT
Doesn't solve the problem itself, but here's a good workaround to VS.NET's
gnarly web projects implementation:
http://www.pluralsight.com/fritz/Samples/aspdotnet_without_web_projects.htm

Signature
---------------------------------------------------
Automate your software builds with Visual Build Pro
http://www.visualbuild.com/
> I'm running Windows Server 2003, IIS 6.0, and VS 2003. I have an
> ASP.NET project I previously created, and went to open it back up to
[quoted text clipped - 13 lines]
>
> Help!