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

Chapter 5. Developing Solutions under Source Control

In this chapter we are going to learn about the source control operations we use daily in our development activities. We will start by setting up a new workspace and get the solution from the SourceSafe database. Then, we will add new files to the solution, check them in, examine their history, and get the latest versions.

We will also explore the team cooperation models and see what are the differences between them, their advantages and disadvantages, and operations such as item comparison, undoing changes, file merging and pinning, and conflict resolution.

Towards the end, we will see how to search for files in the database, how to share files across multiple projects, how to move files and projects, how to rebind projects, and how to move and delete projects and files.

Setting up the Workspace

If you remember, we've talked about workspaces back in Chapter 1. While the main solution is contained in a central SourceSafe database on a server...