Editing a solution on two machines

[Guest]

Hi all,

First apologies for the off topic question, this is a sourcesafe question,
but the Sourcesafe groups just don't get answers, so I thought I'd try your
patience here <G>

I have a solution (currently 2 pojects) at one site that I want to be able
to take to another site and edit there. Both sites use Sourcesafe and are
completely separate.

How can I achieve this without causing conflicts between the two Sourcesafe
databases?

Any help appreciated,

MFK.

 

[Guest]

Hi,
Actually your question is not clear..

do you mean than you want to use and existing source safe project in another
solution loaded on the source safe with keeping the priginal project without
any update ?

Regards,
Husam Al-A'araj
www.aara.net

 

[Guest]

Sorry for the lack of clarity, I'll give it another go,

I want to be able to edit one solution, as a complete and separate solution,
on two separate systems (one at a time only and carrying a copy of the
solution files between them), but have both sourcesafe databases made
"up-to-date" when I open the solution on each machine.

I hope that explains it a little better

 

[Chris V]

Sorry for the lack of clarity, I'll give it another go,

I want to be able to edit one solution, as a complete and separate solution,
on two separate systems (one at a time only and carrying a copy of the
solution files between them), but have both sourcesafe databases made
"up-to-date" when I open the solution on each machine.

It sounds like you're asking how to use one solution (whether the same
files or individual copies) to keep two independent source control
databases updated. Is this correct? If so, there is no *efficient*
way to do this that I'm aware of. The normal way to detach a solution
from a single source control database in Visual Studio is by using the
File -> Source Control -> Change Source Control option and clicking
"Unbind" for all projects in the solution. This would allow you to
remove the VSS bindings and then add your solution to a different VSS
database, but the relationship is lost at that point, and I'm not
aware of any way to simply re-import it later and have it merge with
the original VSS data as a simple bulk update. I'm sure someone out
there has a creative way to do it, but it would be far from efficient,
if it worked at all.

 

[Guest]

Thanks for the response Chris.

this is pretty much what I had suspected (Do what ?!? No way!)

I'll just have to live with it being up to date in one database

MFK