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

Summary


In this chapter we took the first step towards working under source control—adding a new solution to the SourceSafe database.

After setting up a new database, we must add it to our database list by connecting to it either using the LAN or the Internet. When using the LAN we use SourceSafe Explorer or Visual Studio with the LAN plug-in. When using the Internet, the only option is Visual Studio with the internet plug-in. Then, we open the database and check whether everything is in order.

When adding the solution to the database, however, the only option is to use Visual Studio because, since we are going to do all the development using it, Visual Studio knows what is best on how to handle the solution. It only adds the necessary solution files to the database, avoiding problems related to local user files that should not be subjected to source control such as user settings and binary output files that are large and can be built at any time.

The solution structure is matched in the database...