Using Visual SourceSafe – Several Important Concepts

This article is a part of SourceSafe / VSS Tutorial

Navigation links:
VSS Database/Repository
Master Copy and Local Copy

VSS Database/Repository

VSS database/repository is the central place where all files, history, project structures, permission and user information are stored. VSS database consists of hundreds of or even thousands of individual files with some strange names like aaaaaaa.a or baaaaaaa,a. The format of the VSS database is unknown to the public since Microsoft never published the format/specification.

Working Folder

Working folder is the specified corresponding folders on a user’s local computer used to store files when working with VSS projects. By default, the files are retrieved to the corresponding working folder when a user does Get or Check Out. A user can make changes to files in the working folder and then checks the modified files back into the VSS database for version tracking.
Working folder is required for many VSS operations. For example, if a working folder is not set, when you do Get Latest Version, VSS will prompt you to set a working folder for the current VSS project or else the Get operation cannot continue.

Master Copy and Local Copy

A master copy is a copy of a file stored in a VSS database. A local copy is a copy of a file stored in your working folder on your local computer. The reason why the copy in VSS database is called a master copy is that the VSS database is the central point for file synchronization. After you make changes to your local copy, you need to check the file into the VSS database so that your team member can access the file content changed by you. You can do Get Latest Version to retrieve the latest version. More importantly, before making any changes, you need to Check Out the file first. The Check Out operation marks the file in the VSS database as checked out and retrieves the latest version to your local hard disk.
Most version control systems have similar concepts with the ones in VSS.

SourceAnywhere - the SQL Server-based SourceSafe Replacement The SQL Server-based Source Control Software Designed to be a SourceSafe Replacement SourceAnywhere for VSS - the Fastest SourceSafe Remote Access Tool Recommended by Microsoft The Fastest SourceSafe Remote Access Tool Recommeded by Microsoft

Links:
Previous article <<<<: What can SourceSafe do?
Next article >>>>:  Basic operations of SourceSafe / VSS
SourceSafe How To series home page: VSS / SourceSafe Tutorial

2 thoughts on “Using Visual SourceSafe – Several Important Concepts

  1. You have to install “Netsetup” tool on client workstation to access VSS from Server. You can access the setup file from the server machine “C:/Program Files/VSS/Netsetup”path. Before that, you have to provide share permission to the VSS folder. Admin has to create the developers list in VSS Admin login. Version Numbers will be in numerical format like ver1..ver2..verN like that…

  2. Kevin,

    I work in an IT Development Department and we want to check to make sure that we have Microsoft Visual Source Safe set up correctly. We are pretty certain that we do not have it setup the right way.

    Can you tell me what the recommended method of setup and configuration is for a development team of 6-7 programmers? Also, what are all of the version numbers for Visual Source Safe?

    Do users have to be setup on each database or is there a way to setup users on multiple databases at one time.

    Thanks for all of your help!

Comments are closed.