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

Comparing Versions

Because history applies to both files and projects, we can compare files and projects as well.

Comparing File Versions

Viewing changes between two file versions is a simple operation. If you remember from Chapter 1, the difference between two file versions is called a delta. When reconstructing one specific version, SourceSafe combines all the deltas up to the desired version.

We've earlier seen the history for the RoomManager.cs file and how it has evolved over the course of three versions. Let's take a look now at the differences between these versions.

To see the differences between file versions, we are going to open the same History dialog. Only now, we will use the Diff command.

To see the differences between the last version in our workspace and the first version in the database, I will open the History dialog using the View History command and select the first version in the list, version 1 as shown in the following figure:

Then I will click the Diff button on the...