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

Changing the Team Version Control Model


We examined the team cooperation checkout models in Chapter 5. If during development you decide to change the checkout model for the database, you can do so by using the Option window in the Visual SourceSafe Administrator.

To enable the multiple checkout model, (enabling multiple users to check out a file at the same time) select the Allow multiple checkouts option. To restrict the checkouts only to the latest versions, (force a get latest operation) select the Only allow checkouts of the latest version option.

The Only allow checkouts of the latest version option is new in Visual SourceSafe 2005 and it is designed especially for disconnected scenarios as we've seen in Chapter 6. It controls the file version that will be checked out as a result of a check-out operation.

If it is enabled, only the latest database file version can be checked out. This is for compatibility with older SourceSafe versions and can lead to data loss.

If it is disabled, local file versions can be checked out also. The ability to check out local file versions is critical when reconnecting to the database after checking out files in disconnected mode because it avoids manual file merges and possible data loss.

To avoid data loss keep this option disabled.

Note

Because initialization and customization data is read by SourceSafe clients only while starting up, these options will take effect only after the logged-in users restart any opened SourceSafe client and Visual Studio.