It sounds like you want everyone to work on the same physical file (every
developer going to the same share on the network, accessing/changing the
same file). Don't do this. Each developer gets their own working version of
the source code, which they can change as they please by checking it out.
This just gives them a writable copy. When they check it in, it gets changed
in the VSS database and the next time another developer gets the latest
version of files from that project, they'll get the changes.
To allow multiple developers to checkout the same file at the same time,
turn on multiple checkout in the VSS admin program if it's not already
turned on. If two developers make changes (both checked out at the same
time), then the second developer might need to merge changes if there are
conflicts in the files where the first developer changed things and the
second developer changed things.
Go slowly with this so that you understand what's going on. One file, two
developers, and see what you think should happen and then what actually
enviornment and we are just testing various features of VSS. If a file is to
be worked upon by 3 people simultaneously than what should be done. We don't
want the file to be shared into other folders as this file is not required
to be added into those projects.I tried to create branches but that option
disables after creating just one branch under the same folder,which means
only one branch can be worked on under a folder at a time.Our requirement
and we also want to retain the master copy of the code. what is to be done?
client machines, What should we do?