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

Checking In to the Database

After successfully building the solution, I will check in the changes I've made so far. All pending changes to the database are referred to as pending checkins. At any time, we can view the pending checkins by looking in the Pending Checkins window in Visual Studio. The Pending Checkins window can be activated using the View | Pending Checkins command or by right-clicking on the solution in the Solution Explorer window and using the View Pending Checkins command.

The window shows all the changed files along with the change type. We can see all the newly added files and the edited files. The figure above contains only a subset.

The Comments button in the Pending Checkins window shows and hides the Comment text box.


Best Practice

Every check in can and should be associated with a comment that explains what was modified. Give a detailed explanation about what was changed and why, as it will help in easily identifying bugs and other issues.

After entering the check...