problem connecting to existing projects on shared server

[scottrm]

We have multiple developers all using a shared development server. Recently
we have migrated to a new server. I copied all the project folders across
and created virtual directories mapped to and with the same name as the
project folder (same as the old server) but when I create a new solution and
try to add the existing projects from the new development server I get the
following message.

"Unable to open Web project 'qssweb/CTSubs'. The file path
'J:\QSSWeb\CTSubs' does not correspond to the URL
'http://Localhost:/qssweb/CTSubs'. The two need to map to the same server
location. HTTP Error 404: Object Not Found"

The file share path in the above mesage is correct but the url is looking
on localhost not the development server. Any idea on how to change this? I am
aware of the article
http://support.microsoft.com/default...;EN-US;Q320265 but this only
seems to apply to creating new projects (which I can do ok) but not
connecting to existing projects.

--
Scott

[Steven Cheng[MSFT]]

Hi Scott,

As for the problem you mentioned, the file shared path
'J:\QSSWeb\CTSubs' is the physical path of the virutal dir on your new
server ,yes?
the http://Localhost:/qssweb/CTSubs url is the original setting which is
stored in the web project's project info file.

Is your web project a C# project or VB.NET? The Webapplication 's
WebUncWeb Path is configured in the
webinfo file, if you're using C# , you should open the
"ProjectName.csproj.webinfo" file, and you'll find the following element in
it:
<VisualStudioUNCWeb>
<Web URLPath = "http://localhost/Virutal Dir /project name.csproj" />
</VisualStudioUNCWeb>

Also, if the project is contained in a Solution, there is also such info in
the ".sln" file. You also need to adjust it to the correct value according
to your new server's virutual dir path.

Thanks.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx