Microsoft Visual SourceSafe: Difference between revisions

Revision as of 19:33, 5 June 2018

Revision as of 02:35, 10 June 2018

Line 37:

==Overview==

SourceSafe was initially not a client/server [[Source Code Management]], but rather a ''local'' only SCM system. 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 [[Source Code Management|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 [[Source Code Management|SCM]] products, including support for [[atomic commit]]s of multiple files ([[Concurrent Versions System|CVS]] has the same problem as it is built upon the original [[Revision Control System|RCS]]). SourceSafe inherits its ''shared'' functionality using direct remote file system access to all the files in the repository. This, together with historic bugs in the codebase, occasionally led to SourceSafe database corruption, a problem noted by Microsoft.<ref>{{cite web|title=SourceSafe database corruption|url=http://msdn.microsoft.com/en-us/library/bb509342%28v=vs.80%29.aspx|publisher=Microsoft|accessdate=18 Dec 2014}}</ref>

Starting with VSS 2005, Microsoft added a [[client–server]] mode. In this mode, clients do not need [[write access]] to a [[Server Message Block|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|date=June 2007}}

Line 102:

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.<ref>{{cite web|last=Krill |first=Paul |url=http://www.infoworld.com/d/developer-world/microsoft-looks-move-sourcesafe-users-newer-technology-983 |title=Microsoft looks to move SourceSafe users to newer technology &#124; Developer World |publisher=InfoWorld |date=2009-09-30 |accessdate=2012-04-13}}</ref><ref>{{cite web|url=http://msdn2.microsoft.com/en-us/library/aa302175.aspx |title=Visual SourceSafe Road Map |publisher=Msdn2.microsoft.com |accessdate=2012-04-13}}</ref> There is a [http://code.msdn.microsoft.com/KB976375 hotfix] so existing SourceSafe customers can use SourceSafe with Visual 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.<ref>http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=sourcesafe&Filter=FilterNO</ref>

==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==

Line 120:

==References==

{{reflistReflist}}

==External links==

* [http://msdn2.microsoft.com/en-us/vstudio/aa700907.aspx Product Overview]

{{Revision control software}}