Jump to content

Microsoft Visual SourceSafe: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Gpeji (talk | contribs)
11 edits
→‎Future: Changed to more fitting title
Line 88: Line 88:
The Microsoft Developer Division is now using the new [[Visual Studio Team System]] for most of its internal projects,<ref>[http://msdn.microsoft.com/vstudio/teamsystem/support/faqs/teamsystem_faq/]</ref>{{Citation broken|date=May 2009}} although a VSS transcript implied that other large teams use "a mix of customized in-house tools."
The Microsoft Developer Division is now using the new [[Visual Studio Team System]] for most of its internal projects,<ref>[http://msdn.microsoft.com/vstudio/teamsystem/support/faqs/teamsystem_faq/]</ref>{{Citation broken|date=May 2009}} although a VSS transcript implied that other large teams use "a mix of customized in-house tools."


==Future==
==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,<ref>[http://blogs.msdn.com/b/richardb/archive/2007/12/03/vs-2008-and-sourcesafe-q-a.aspx]</ref> but is not included with Visual Studio 2008 Team System.
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,<ref>[http://blogs.msdn.com/b/richardb/archive/2007/12/03/vs-2008-and-sourcesafe-q-a.aspx]</ref> but is not included with Visual Studio 2008 Team System.


Revision as of 23:20, 20 April 2011

Visual Source
Developer(s)Microsoft
Initial release1994 (1994)
Stable release
2005 (8.0.50727.42) / October 2005 (2005-10)
Operating systemWindows
TypeRevision control
LicenseProprietary commercial software
Websitewww.microsoft.com

Microsoft Visual Source Safe (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 Source Safe 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. Version 4.0 and later versions made significant architectural changes, such as replacing the previously-used database layer.

Overview

SourceSafe was initially not a client/server SCM, 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. [citation needed]

Starting with VSS 2005, Microsoft has added a client–server mode. In this mode, clients do not need write access to an 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.[citation needed]

Versions

Version Date
2005 October 2005
6.0 2002
5.0
4.0

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 Visual Studio Team System for most of its internal projects,[8][full citation needed] 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 Visual Studio 2010, Microsoft no longer distributes Visual SourceSafe. Microsoft now offers Team Foundation Server Basic for smaller development teams.[10][11] There is a hotfix so existing SourceSafe customers can use SourceSafe with Studio 2010.

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

Books on Visual SourceSafe

  • 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

  1. ^ De Smet, Alan (2009-04-15). "Visual SourceSafe: Microsoft's Source Destruction System". Retrieved 2010-09-19. {{cite web}}: Check |authorlink= value (help); External link in |authorlink= (help)
  2. ^ Bolton, Michael (2003-01-28). "Visual SourceSafe Version Control: Unsafe at any Speed?". Retrieved 2010-09-19.
  3. ^ "Company News; Microsoft Says It Has Acquired One Tree Software". The New York Times. November 16, 1994. Retrieved 2007-11-21.
  4. ^ "Best Practices for Preventing Data Corruption". MSDN.
  5. ^ [1]
  6. ^ [2]
  7. ^ Doar, Matthew B. (2005). Practical Development Environments. O'Reilly. p. 73. ISBN 0596007965. {{cite book}}: Cite has empty unknown parameter: |coauthors= (help)
  8. ^ [3]
  9. ^ [4]
  10. ^ http://www.infoworld.com/d/developer-world/microsoft-looks-move-sourcesafe-users-newer-technology-983
  11. ^ Visual SourceSafe Road Map
  12. ^ Microsoft Product Lifecycle Search
Retrieved from "https://en.wikipedia.org/w/index.php?title=Microsoft_Visual_SourceSafe&oldid=425083787"