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
Credits
About the Author
About the Reviewers
Preface

Versions and History


As we've seen in Chapter 1, a fundamental characteristic of SCM tools is file versioning and history management. During the development process, files in the database change and evolve as the project evolves. Files are modified, renamed, and moved from one folder to another, new files are added, and others are deleted. All these operations are part of the day-to-day work. The SourceSafe database keeps a track of these operations and provides the option to see the state at any time in the past since the solution was first added to Source Control.

Each time a file is added or changed and checked in to the database, a revision is created. Thus, a file evolves as a succession of revisions, referred to by successive numbers such as 1, 2, 3, and so on.

File Versions and History

Let's see, for example, the history of the BusinessLogic project file in the OrbitalHotel solution. To view the history of a solution resource we have to right-click on it and then use the View History...