Visual sourcesafe

Visual Source
Developer(s) Microsoft
Initial release 1994 (1994)
Stable release 2005 (8.0.50727.42) / October 2005 (2005-10)
Operating system Windows
Type Revision control
License Proprietary commercial software
Website

Microsoft Visual SourceSafe (VSS) is a source control software package oriented towards small software development projects. Like most source control systems, SourceSafe creates a virtual library of computer files. While most commonly used for source code, SourceSafe can actually handle any type of file in its database, but prior versions have been shown[1][2] to be unstable when confronted with large amounts of non-textual data (images, binary executables, etc.).

History

SourceSafe was originally created by a company called One Tree Software. One Tree SourceSafe had gone through several releases in their 1.x to 2.x cycles, supporting DOS, OS/2 (with a Presentation Manager GUI), Windows, Windows NT, Mac, and Unix. When Microsoft bought OneTree in 1994,[3] they immediately ceased development on all versions except for Windows. Microsoft "Visual SourceSafe 3.1", a Windows 16-bit-only, rebranded One Tree 3.0 version, was briefly available before Microsoft released a Version 4.0.

Overview

SourceSafe was initially not a client/server Source Code Management, but rather a local only SCM. Architecturally, this serves as both a strength and weakness of design, depending on the environment it is used in. It allows a single user system to be set up with less configuration than that of some other SCM systems. In addition, the process of backing up can be as simple as copying all of the contents of a single directory tree. For multi-user environments, however, it lacks many important features found in other SCM products, including support for atomic commits of multiple files (CVS has the same problem as it is built upon the original RCS). SourceSafe inherits its shared functionality using direct remote file system access to all the files in the repository. This, together with a bug where the code is using old memory after a call to reallocate, are contributing factors to why SS databases sometimes go bad.

Starting with VSS 2005, Microsoft has added a client–server mode. In this mode, clients do not need write access to a SMB share where they can potentially damage the SS database. Instead, files must be accessed through the VSS client tools - the VSS windows client, the VSS command-line tool, or some application that integrates with or emulates these client tools.

Versions

Version Date
6.0  ??
2005 October 2005

Criticism

Visual SourceSafe's stability is criticised due to the way Visual SourceSafe uses a direct, file-based access mechanism that allows any client to modify a file in the repository after locking it. If a client machine crashes in the middle of updating a file, it can corrupt that file.[4] Many users of Visual SourceSafe mitigate this risk by making use of a utility provided by Visual SourceSafe that checks the database for corruption and, when able, corrects errors that it finds.

Microsoft in-house use

Although "eating their own dog food" is often said to be part of Microsoft's culture, VSS appears to be an exception; it is widely rumored[5][6] that very few projects within Microsoft rely on VSS, and that the predominant tool is SourceDepot. According to Matthew Doar:[7]

Microsoft itself used an internally developed version of RCS named SLM until 1999, when it began using a version of Perforce named SourceDepot.

The Microsoft Developer Division is now using the new Team Foundation Server for most of its internal projects,[8][broken citation] although a VSS transcript implied that other large teams use "a mix of customized in-house tools."

Updates

An updated version called Visual SourceSafe 2005 was released in November 2005, promising improved performance and stability, better merging for Unicode and XML files, as well as the ability to check files out over HTTP. It was included with Visual Studio 2005 Team System editions,[9] but is not included with Visual Studio 2008 Team System.

At the same time, Microsoft also introduced a source control and project lifecycle management product called Team Foundation Server, which is part of Visual Studio Team System. This product addresses many of Visual SourceSafe's shortcomings, making it suitable for larger teams requiring high levels of stability and control over activities.

With hotfix so existing SourceSafe customers can use SourceSafe with Studio 2010.

The final version of the product, Visual SourceSafe 2005, retired from mainstream support on 10 July 2012 with extended support ending on 11 July 2017.[12]

Further reading

  • Visual SourceSafe 2005 Software Configuration Management in Practice (Packt Publishing, 2007)
  • Real World Software Configuration Management (Apress, 2003)
  • Essential SourceSafe (Hentzenwerke Publishing, 2001)

See also

References

External links

  • Product Overview
  • Features Overview
  • Microsoft SourceSafe 6.0 General Q & A
  • Microsoft SourceSafe 6.0 Technical FAQ
  • Product Documentation
  • Microsoft VisualSourceSafe Road Map This article gives an overview of Visual SourceSafe and provides a look at where this technology is headed in the future
  • SourceSafe Team's WebLog
  • SourceSafe Best Practices Outlines recommended practices to help prevent data corruption in Microsoft Visual SourceSafe.
  • Team Development with Visual Studio .NET and Visual SourceSafe Guidance and recommendations by the Patterns and Practices Team
  • Visual SourceSafe 2005 Web Cast Source Control and Team Development Using Visual Studio .NET and Visual SourceSafe
  • Visual SourceSafe 2005 at MSDN
  • Visual SourceSafe Version Control: Unsafe at any Speed?
  • Visual Studio 6.0 SP6 for Latest VSS Service Pack (6.0d)
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.