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

Getting the Latest Versions


To keep the local workspace up to date with the contents of the database, we must get the latest versions for the files in the database. This operation can be applied to a single file, multiple files, projects, or solution files.

Let's see how, in my example, other developers can get the latest solution version that includes the files I've added earlier.

Before I've checked in the changes to the solution, their workspaces have the solution contents prior to my check in.

To get the latest version for all the projects in the solutions, we have to right-click the solution in Solution Explorer and click on the Get Latest Version (Recursive) command.

Visual Studio will retrieve recursively the latest versions for all the files in the solution including projects and files. When applied to any file container (solution, project, or folder), the Get Latest Version (Recursive) command gets all the items under the selected item. Looking at the Output window for Source Control...