Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Visual SourceSafe 2005 Software Configuration Management in Practice

You're reading from   Visual SourceSafe 2005 Software Configuration Management in Practice Best practice management and development of Visual Studio .NET 2005 applications with this easy-to-use SCM tool from Microsoft

Arrow left icon
Product type Paperback
Published in Feb 2007
Publisher Packt
ISBN-13 9781904811695
Length 404 pages
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (15) Chapters Close

Visual SourceSafe 2005 Software Configuration Management in Practice
Credits
About the Author
About the Reviewers
1. Preface
1. Controlling the Evolution of Software Products FREE CHAPTER 2. The SourceSafe 2005 Architecture 3. Creating a Service-Oriented Application 4. Adding Solutions to the SourceSafe Database 5. Developing Solutions under Source Control 6. Working from Remote Locations 7. Managing the Software Development Lifecycle Installing Visual SourceSafe 2005 Creating and Configuring SourceSafe Databases Database Maintenance

Summary


In this chapter we've seen how to manage the software development lifecycle using SourceSafe.

When developing a product we go through several milestones. A milestone is a point in time representing a key or important event in the life of a product. We mark milestones using labels so we can reproduce their configuration later when needed. We've seen how to create labels and how to get labeled versions and create persistent solution configuration snapshots in the SourceSafe database by sharing and pinning.

Then, we spoke about building either nightly or continuously, testing, and releasing a new product version. After releasing a new product version we have to maintain it while advancing development towards a new version. To be able to do this we have to conduct these efforts in parallel. We need to branch a new maintenance line for the maintenance effort while ongoing development is conducted in the mainline. After fixing bugs in the maintenance line we have to fix them in the mainline...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image