Book Image

Visual SourceSafe 2005 Software Configuration Management in Practice

Book Image

Visual SourceSafe 2005 Software Configuration Management in Practice

Overview of this book

Why is Software Configuration Management important?Software Configuration Management (SCM) is the discipline of managing the building and modification of software through techniques including source-code control, revision control, object-build tracking, and release construction. SCM involves identifying the configuration of the software at given points in time, systematically controlling changes to the configuration, and maintaining the integrity and traceability of the configuration throughout the software development lifecycle.Software Configuration Management is one of the first skills a serious developer should master, after becoming proficient with his or her development tools of choice. Unfortunately, this does not always happen because the subject of SCM is not commonly taught in either academic or company training.When developing software, you need to have a manageable team development effort, track and maintain the history of your projects, sustain parallel development on multiple product versions, fix bugs, and release service packs while further developing the application. This is where the concepts of Software Configuration Management come into play; SCM is about getting the job done safer, faster, and better.Visual SourceSafe has a long history behind it. The previous versions were either loved for their ease of use and integration with other Microsoft products, or hated because the headaches caused by using them improperly. This book will help you to avoid such problems.
Table of Contents (15 chapters)
Visual SourceSafe 2005 Software Configuration Management in Practice
About the Author
About the Reviewers

The Visual SourceSafe Database

The central repository for project resources is the Visual SourceSafe database. The physical database storage is the file system on the SourceSafe server machine. The database is accessed by the clients through a Universal Naming Convention (UNC) file share on the server, for example:


The structure of a typical SourceSafe database uses the following file and folder organization:

User and database options are kept in initialization (.ini) files.

Data Folder

The data folder holds the database data. It contains many physical files with obfuscated names like DCBAAAA that store the real source files added to the database and their history. The data folder is organized in a series of folders from a to z and additional labels, locks, and loggedin folders containing database metadata.

For every file in the project, Visual SourceSafe creates a pair of files in the a to z folders, one with an extension and one without an extension. The file without...