Process of separating a shared file among two or more branches. During branch creation, the share link is broken for the shared file. After branching, files will have a shared history up to a certain point, and divergent histories after that time.
File that has been reserved for modification, using the Check Out command. Checking out a file copies its latest version into the user's working folder. In the default work style, Visual SourceSafe allows only one user at a time to check out a file.
Formatting option used with keyword expansion in a file. This option uses two colons instead of one in the keyword instructions. It instructs Visual SourceSafe to align columns of keyword information for a more readable display.
One of two work styles available for use of a Visual SourceSafe database. This work style enables multiple checkouts of the same file in a team environment. Using this work style, a user can copy a file from the database, modify it in the working folder, and merge it with changes made by other users. See also Lock-Modify-Unlock.
Text at the beginning of a file that contains the revision number of the file, the author, the date and time of last modification, and so forth. This information usually appears as comments in programming language files so that it does not interfere with compiling.
Record of changes to a file or project since it was initially added to a Visual SourceSafe database. The database can return to any point in the file history and recover the file as it existed at that point.
A unified environment for software development, which includes a set of integrated development tools. An example of a system that provides an integrated development environment is Microsoft Visual Studio.
A process that Visual SourceSafe uses to automatically replace a keyword with meaningful header information when files are checked in or added to a database. For example, the string "$Revision: $" instructs Visual SourceSafe to expand the Revision keyword automatically with the current file version number.
Copy of a file stored in a user's working folder on the local computer. The local copy differs from the master copy if the local copy is changed since the last checkout, or if the master copy is changed by another user while the local copy is checked out.
One of two work styles available for use of a Visual SourceSafe database. This classic work style enables exclusive checkout of a file by one user at a time. Using this work style, a user can copy a file from the database and lock it for access by other users, modify it in the working folder, and then check in the file, which unlocks it for access by other users. See also Copy-Modify-Merge.
Ensuring that two processes do not affect the same file or project in a database at the same time. Visual SourceSafe applies native locking, which applies native operating system functions. Visual SourceSafe can also be set to use lock files that create temporary files in the Locks directory included in the Visual SourceSafe installation path.
Process of combining differences in two or more changed copies of a file. Merging creates a new version of the file made up of the results of difference reconciliation. Merging can occur when the user merges two branches, using the Merge command, or when the Check In or Get Latest Version command is used.
Simultaneous Check Out operations by two or more users, or multiple checkouts to different locations by one user. The database administrator must enable multiple checkouts to create a Copy-Modify-Merge work style in a team environment.
Group of related files, for example, all files required to develop a software component. Files can be grouped within a project to create subprojects. Projects can be defined in any way meaningful to the user(s), for example, one project per version, or one project per language. Projects are organized in the same way as file directories.
Rights to use a Visual SourceSafe project, for each database user. Visual SourceSafe include project rights include Read, Check Out/Check In, Add/Rename/Delete, and Destroy. Each succeeding right includes all rights preceding it. The Destroy access right provides unlimited access.
File marked as read-only in its file attributes. Such a file can be viewed in an appropriate text editor, but cannot be modified. Visual SourceSafe marks a file as read-only when processing Check In and Get Latest Version commands.
Term applied to an operation on a project and all the files and subprojects of that project. For example, you can use the Check Out command recursively to check out all files in the project list simultaneously and avoid selecting each file individually.
Change storage technology used by Visual SourceSafe. The reverse delta technology stores incremental changes to a baseline file instead of storing each successive version of the file in its entirety. Visual SourceSafe uses the current version of a file as the baseline, and saves changes from previous versions. Use of reverse delta technology reduces disk storage requirements and speeds up file access.
An optional file system folder that contains current copies of all files in a project. The shadow folder provides a location from which to view the files without accessing the Visual SourceSafe database and serves as a convenient place to build or compile the project.
Link between copies of the same file that are shared among two or more projects. Visual SourceSafe uses the share link to update the shared file with any checked-in changes, regardless of the project from which the file was checked out.
Inheritance of initialization variables by Visual SourceSafe subprojects. Each subproject inherits the variables of its parent project and the initialization file arrangement used by the parent project.
Program used by the database administrator to control the location of the database, the user list, sharing permissions and project rights for each user, and enable Web Service and LAN Service. The program also allows the database administrator to perform maintenance on the database and optimize its performance.
Central database where all master copies, history, project structures, and user information are stored. A Visual SourceSafe project is always contained in one database, and multiple projects can be stored in one database. Multiple databases can be used and accessed from the client programs.
Folder on a user's local computer that is used to store files when they are checked out of a Visual SourceSafe database. A user makes changes to the files in the working folder and then checks the modified files back into the Visual SourceSafe database for version tracking.