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
About the Author
About the Reviewers

Sharing Files

Sometimes we have one or more files that we need to keep in different projects but we want them to remain the same in all of them. The solution to such cases is to share a file between multiple projects. Changing one file will cause it to change in all the places it is shared.

One such case can be the strong name file we use to sign our assemblies. In this example I need the same file to sign all the assemblies.

I've added the OrbitalHotel.snk file at solution level but I want to keep it in the projects also.

SourceSafe provides the Share function for such cases. Depending on the client application we can share files using the Visual Studio LAN or internet plug-in or the Visual SourceSafe Explorer.

Using Visual Studio with the LAN Plug-In

To share a file using the LAN plug-in, we have to select first the destination folder. After selecting the destination folder we can use the Share command in the Source Control toolbar.

Using the Share command displays the Share to dialog: