Re: Mapping issue on Visual SourceSafe
- From: "Anthony Jones" <Ant@xxxxxxxxxxxxxxxx>
- Date: Sun, 22 Jun 2008 08:28:20 +0100
"Curious" <fir5tsight@xxxxxxxxx> wrote in message
news:f1c698b0-081b-46b8-9a94-9315fe0c1836@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have the same .NET program developed on two machines, therefore, two
different versions, call them A and B.
There are following differences between A and B:
1) They have differences in source code;
2) Since A is developed in Visual Studio 2005 with .NET 2.0, but B is
developed in Visual Studio 2003 with .NET 1.1, the project files are
different.
I've been checking in the code from A to Visual SourceSafe from the
machine where A is developed. Now I want to check in the code from B
to the project location in VSS. But it has failed.
Here's what happened: When I tried to map B to Visual SourceSafe, it
seemed to require me to map both the hard-drive folder and the project
file (.sln) to VSS. While the folder location seemed to be mapped
successfully, the .sln file failed to match. It's "invalid".
Any advice on how to map B to an existing project location in VSS?
Source control management inside Visual studio is maddening at times and is
worse in VS 2003.
VS 2003 uses a project file to track content in a web, whereas VS 2005
simply uses the folder contents.
My advice would be a) Use 2005 and ditch 2003 (unless you still need to
support 1.1 for some reason) and b) when initialising a new source safe with
existing source use Visual SourceSafe directly not Visual Studio.
This approach allows you configure the layout of project and solutions in a
way you find acceptable rather than putting up with studio's choices.
--
Anthony Jones - MVP ASP/ASP.NET
.
- Follow-Ups:
- Re: Mapping issue on Visual SourceSafe
- From: Jon Skeet [C# MVP]
- Re: Mapping issue on Visual SourceSafe
- References:
- Mapping issue on Visual SourceSafe
- From: Curious
- Mapping issue on Visual SourceSafe
- Prev by Date: Visual Studio 2005 & Vista 64 issues
- Next by Date: Re: Mapping issue on Visual SourceSafe
- Previous by thread: Mapping issue on Visual SourceSafe
- Next by thread: Re: Mapping issue on Visual SourceSafe
- Index(es):
Relevant Pages
|