Printable View
Hi,
We are a small team working on the same prog, and living in different towns with our DSL connection.
How can we use sourcesafe in our case (one of us will host the database) ?
We didnt find anything clear & simple to do that...
Thx very much for any proved & tested solution.
A+
At one of my previous jobs, The lead programmer was close to leaving because managment wanted to open their sourcesafe database over the internet for a consulting company. He felt that it was basically an invitiation to malicious hackers.
I would advise you guys to assign out modules that each person can work on, and, when a revision is ready for insertion into the project, it should be mailed to each person working on the project for revision. Once it is QAed by everyone, insert it as a final copy. If a bug arises, and is fixed, repeat the process. Also, I would designate one person as a source bank, who keeps a complete copy of the source that contains all of the QAed modules, and no other changes. Every month or so, a copy of this source should be distributed to all of the programmers.
While this seems to be a bit awkward, it is much more secure, and if one persons computer dies, you still have copies of the source.
Z.
use a prgraom called SourceOffSite
one of the best programs ever...
it mimics vss but through internet :)