All,
We have an existing ASP.NET site, set up as follows:
URL: www.somecompany.com/home/
phyiscal directory: wwwroot/home/
sourcesafe project: $/home/
We are going to upgrade this site, a portion at a time, over the next year
or so. To separate the legacy from new code, we'd like to put the new code
in a new Visual Studio (and sourcesafe) project. But we need the pages to be
browseable via the same URL as the old pages (www.somecompany.com/home/),
ie, the new versus old projects should not be apparent to the user.
We tried putting the new project in the same physical directory as the old
project, so that it would share the same virtual directory. However, that
was not very popular with sourcesafe. It seems to have trouble with two
Visual Studio projects being in the same directory. When we try to bind the
projects in Visual Studio, it is unable to do so.
Any suggestions?
Thanks, Mike
Dmitry Goncharenko [MSFT] - 30 Oct 2003 18:00 GMT
Hi Mike,
Even though VSS allows to have the same working folder for different
folders in VSS DB, VS source control integration requires one-to-one
mapping between local and DB folders.
Therefore as long as your new project files are in $/Home then the files
must be in wwwroot/home. If you want to use say $/newhome for the new pages
then the files should go to another folder locally, say wwwroot/home/new.
Dmitry Goncharenko (dgonchREMOVETHECAPS@microsoft.com), Visual Studio Core
Team
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
> From: "Mike Best" <mbest@saklogistics_nospam.com>
> Subject: Multiple VS projects in one virtual directory
[quoted text clipped - 23 lines]
>
> Thanks, Mike