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

Deleting, Recovering, and Purging Files


When we (think) no longer need a file, we can delete it.

To delete a file use the delete key on the keyboard. Visual Studio displays a warning message telling us the file will be deleted permanently.

It will also display the following dialog asking whether to delete the file both locally and in the SourceSafe database or only locally:

To delete the file in both locations select the first option. We will have to make sure we check in the changes as soon as possible so as to not affect the other users that will not find the file in the database anymore, preventing the previous solution version in the database from building.

To delete the file only locally, we use the second option. When using this option we will have to delete the file manually in the database later.

The file will be deleted permanently from the local workspace (actually put in the Recycle Bin) but it will not be permanently deleted from the SourceSafe database, although it will not be...