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

What Happens after Adding the Solution to the Database


After adding the solution to the database, you will see specific source-control icons next to the solution and every project and file in the solution. The solution, projects, and files all have checked-in status, indicated by the blue lock icon as shown in the following figure:

The project and solution files have been modified (prior to adding them to the database) to indicate that solution is now controlled.

In addition, Visual Studio creates additional files containing metadata that provide source control integration for the solution and projects. For the solution there will be a<SolutionName>.vssscc file, and for the projects there will be a<ProjectName>.csproj.vspscc file that will also be added to the source control database. Depending on your solution's configuration on the local disk, another file<SolutionName>.vsscc may be added to the source control database (do not confuse this with vssscc). These files contain...