OK... this is a bit long, but I wanted to write it all out at least
for my sake, so I know what I've tried already.
I fixed the .vspcc files -- they were pointing to localhost/mysite
instead of mysite.mydomain.com. There is no .webinfo file in either
project directory. Do I need to fabricate one?
I cleared my VSWebCache and got latest from SourceSafe to the virtual
directories on the server. Made sure that the sites
mysite1.mydomain.com and mysite2.mydomain.com were setup correctly in
IIS, with host headers, etc. Made sure I could browse to a HTML file
on each site.
I opened VS.NET (2003) on my local box and created a blank solution.
Eventually I would like to have the solution in VSS, since that's what
we have been doing on all our projects. But one step at a time.
At this point I have a choice whether to add the first web project
from source control or via open existing project from web. I will try
open existing from web first. I enter the URL mysite1.mydomain.com.
File browser opens to my documents -- obviously it couldn't find a
file share corresponding to the URL. I type in the URL again into the
file name box and get the dialog "The specified web server could not
be accessed. Please enter a valid URL" etc.
I have created a share named "\\myserver\mysite1$" at the mysite1 root
and blown the permissions wide open. So I type the share name into the
box and am able to browse to the share. I click on the project file.
First I get a dialog saying the project location is not fully trusted
by the .NET runtime, no big surprise there. I click OK. Next dialog
says "The project you are trying to open is a Web project. You need to
open it by specifying its URL path." Which of course takes me back to
square one.
What I think is happening is that Visual Studio can't connect the dots
between
http://mysite1.mydomain.com and \\myserver\mysite1$. Is this
where the missing .webinfo file comes in?
Thanks,
-Jonathan Vaught
Senior Applications Developer