Once you save a file to Source Safe the version on your local
drive will be set to read only, it is advised that you do not
manually change this setting and make changes to the file. Instead
you should check it out of Source Safe and then make necessary
modifications. Not following this protocol will result in a situation
where it will be nearly impossible to save the new version into
Source Safe. The program is setup this way by design since if
it did not then two users could easily make modifications simutaneously
and it will be the case that one person's changes will overwrite
those of another. Source Safe is a version control system that
requires users to check a file out before making changes and by
default allows only one user at a time to check a file out. Note
that the system can be changed to allow multiple persons to check
out a file however doing so will create the potential for multiple
versions and an administrator or developer will be required to
manually reconcile the differences between versions.
Checking out a file is relatively straight forward.
Select the project/subproject which the file you want to check
out is located in.
Right mouse click on the file you wish to check out and select
Check Out from the resulting menu.
Enter a comment and select the directory the file should be
checked out to and click OK. Note entering a comment is optional
but it will help other developers/users understand why the file
is checked out.
The following message will be displayed if there is a file currently
stored locally and that file's readonly flag has been removed.
Typically selecting "Replace your local file with the version
from SourceSafe" and clicking OK will not be problematic.
However, be certain there have not been modifications made to
the local file before doing this.
The file will be availible locally to edit/modify and SourceSafe
will indicate it is checked out to you (your username) along
with the directory it is checked out to.
Modifications can now be made to the file, once all desired
modifications have been made be sure to check
the file back in. Not checking a file back in will result
in other developers being unable to perform modifications on
the file. Also, it is recommended you do not move the file to
a different directory, doing so will make it more difficult
for you to check it back in.
@Copyright 2002-2003 Keptin Consulting Services.
All Rights Reserved