Microsoft Visual SourceSafe: Difference between revisions

Revision as of 17:32, 19 December 2020

Latest revision as of 09:33, 29 March 2025

(18 intermediate revisions by 14 users not shown)

Line 1:

{{Short description|Discontinued source control software}}

{{Infobox software

| name = Visual SourceSafe

Line 18 ⟶ 19:

| license = [[Proprietary software|Proprietary]] [[commercial software]]

}}

'''Microsoft Visual SourceSafe''' ('''VSS''') is a discontinued [[source control]] [[computer program|program]], 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 handle any type of file in its [[database]], but older versions were shown<ref>{{cite web

| last = De Smet

| first = Alan

| author-link =

| title = Visual SourceSafe: Microsoft's Source Destruction System

| date = 2009-04-15

| url = http://www.highprogrammer.com/alan/windev/sourcesafe.html

| accessdateaccess-date = 2010-09-19}}</ref><ref>{{cite web

| last = Bolton

| first = Michael

Line 31:

| date = 2003-01-28

| url = http://www.developsense.com/testing/VSSDefects.html

| accessdateaccess-date = 2010-09-19}}</ref> to be unstable when used to store large amounts of non-textual data, such as images and compiled executables.

==History==

SourceSafe was originally created by a North Carolina 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,<ref>{{cite web |url=https://query.nytimes.com/gst/fullpage.html?res=9D0DE4DB1231F935A25752C1A962958260 |title=Company News; Microsoft Says It Has Acquired One Tree Software |work=The New York Times |date=November 16, 1994 |accessdateaccess-date=2007-11-21}}</ref> they immediately ceased development on all versions except for Windows. Microsoft SourceSafe 3.1, Windows 16-bit-only and Macintosh,<ref name="auto">{{cite web|title=MICROSOFT SHIPS SOURCESAFE SOURCE-CODE-MANAGEMENT SYSTEM|url=http://www.thefreelibrary.com/MICROSOFT+SHIPS+SOURCESAFE+SOURCE-CODE-MANAGEMENT+SYSTEM-a016514393|publisher=The Free Library by Farlex|accessdateaccess-date=21 May 2014}}</ref> rebranded One Tree 3.0 versions, were briefly available before Microsoft released a Version 4.0. With the acquisition of One Tree Software, Microsoft discontinued its source code control product at the time, Microsoft Delta.<ref>{{cite web|title=MICROSOFT CORPORATION ACQUIRES ONE TREE SOFTWARE|url=http://www.thefreelibrary.com/MICROSOFT+CORPORATION+ACQUIRES+ONE+TREE+SOFTWARE-a015862138|publisher=The Free Library by Farlex|accessdateaccess-date=21 May 2014}}</ref><ref>{{cite news|last=Gross|first=Daniel|title=Go Configure|url=https://books.google.com/books?id=pgcAAAAAMBAJ&q=%22microsoft+delta%22&pg=PA80|accessdateaccess-date=21 May 2014|newspaper=CIO Magazine|date=November 15, 1995}}</ref> After the acquisition, Mainsoft Corporation developed SourceSafe for UNIX in cooperation with Microsoft.<ref>{{cite web|title=Mainsoft to ship Visual SourceSafe for UNIX|url=http://www.thefreelibrary.com/Mainsoft+to+ship+Visual+SourceSafe+for+UNIX.-a017983649|publisher=The Free Library by Farlex|accessdateaccess-date=21 May 2014}}</ref>

Later, Metrowerks, Inc. developed Visual SourceSafe for Macintosh in cooperation with Microsoft.<ref>{{cite web|title=Metrowerks Signs Exclusive License for Microsoft Visual SourceSafe on Mac OS|url=http://www.thefreelibrary.com/Metrowerks+Signs+Exclusive+License+for+Microsoft+Visual+SourceSafe+on...-a018995298|publisher=The Free Library by Farlex|accessdateaccess-date=21 May 2014}}</ref>

==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|accessdateaccess-date=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}}

=== Versions ===

Line 52:

|-

| 4.0

| September 12, 1995<ref>{{cite web|title=MICROSOFT ANNOUNCES VISUAL SOURCESAFE, AN INTUITIVE CODE-MANAGEMENT SYSTEM|url=http://www.thefreelibrary.com/MICROSOFT+ANNOUNCES+VISUAL+SOURCESAFE,+AN+INTUITIVE+CODE-MANAGEMENT...-a017409497|publisher=The Free Library by Farlex|accessdatearchive-url=https://web.archive.org/web/20140521123851/http://www.thefreelibrary.com/MICROSOFT+ANNOUNCES+VISUAL+SOURCESAFE,+AN+INTUITIVE+CODE-MANAGEMENT...-a017409497 |access-date=21 May 2014|archive-date=2014-05-21 }}</ref>

|-

| 5.0

| October 7, 1996<ref>{{cite web|title=Microsoft Announces Visual SourceSafe 5.0, An Intuitive, Project-Oriented Version Control System|url=http://www.microsoft.com/en-us/news/press/1996/oct96/vss50pr.aspx|publisher=Microsoft|accessdatearchive-url=https://web.archive.org/web/20140610074805/http://www.microsoft.com/en-us/news/press/1996/oct96/vss50pr.aspx |access-date=21 May 2014|archive-date=2014-06-10 }}</ref>

|-

| 6.0

| June 3, 1998 <ref>{{cite web|title=Microsoft Support Lifecycle- Visual SourceSafe 6.0 Standard Edition|url=http://support.microsoft.com/lifecycle/?p1=3036|work=Microsoft Support|publisher=Microsoft|accessdateaccess-date=21 May 2014}}</ref>

|-

| 6.0c (Build 9350)

| 2001<ref>Microsoft Corporation (2001). "Visual SourceSafe 6.0c Readme" (<code>Readmess.htm</code>). ''Microsoft Visual SourceSafe 6.0c'' [CD-ROM].</ref>

|-

| 2005

| January 27, 2006 <ref>{{cite web|title=Microsoft Support Lifecycle - Visual SourceSafe 2005 Standard Edition|url=http://support.microsoft.com/lifecycle/?p1=10433|publisher=Microsoft|accessdateaccess-date=21 May 2014}}</ref>

|}

Line 68 ⟶ 71:

==Microsoft in-house use==

Although "[[Eating your own dog food|eating their own dog food]]" is often said to be part of [[Microsoft#Corporate culture|Microsoft's culture]],<ref name="dogfood">{{cite web|title=Microsoft tests its own dog food|url=http://news.zdnet.com/2100-3513_22-5047467.html| archiveurlarchive-url=https://web.archive.org/web/20070108214545/http://news.zdnet.com/2100-3513_22-5047467.html| archivedatearchive-date=January 8, 2007|work=[[ZDNet]]|publisher=[[CBS Interactive]]|date=July 21, 2003| accessdateaccess-date=October 9, 2005}}</ref> VSS appears to be an exception; it is widely rumored<ref>{{cite web|url=http://weblogs.asp.net/jdennany/archive/2003/07/15/10130.aspx |title=It's all Hype. - Jerry Dennany's Occasional Clue |publisher=Weblogs.asp.net |date=2003-07-15 |accessdateaccess-date=2012-04-13}}</ref> that very few projects within Microsoft relied on Visual SourceSafe before the product was discontinued, and that the predominant tool at the time was [[Perforce|SourceDepot]]. According to Matthew Doar:<ref>{{cite book

| last = Doar

| first = Matthew B.

| author-link =

| title = Practical Development Environments

| publisher = O'Reilly

| year = 2005

| page = 73

| url =

| doi =

| id =

| isbn = 0-596-00796-5}}</ref>

{{quoteblockquote|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 was using [[Team Foundation Server]] for most of its internal projects,<ref>{{cite book

| last = Guckenheimer

| first = Sam

| author-link =

|author2=Neno Loje

| title = Visual Studio Team Foundation Server 2012: Adopting Agile Software Practices: From Backlog to Continuous Feedback (3rd Edition) (Microsoft Windows Development Series)

Line 91 ⟶ 89:

| year = 2012

| page = 241

| url =

| doi =

| id =

| isbn = 978-0-321-86487-1}}</ref> although a VSS transcript{{Citation needed|date=January 2014}} implied that other large teams use "a mix of customized in-house tools."

Microsoft has since moved on to using [[Git]].<ref>{{cite web|url=https://www.theregister.co.uk/2017/05/25/windows_is_now_built_on_git/|title=Windows is now built on Git, but Microsoft has found some bottlenecks|author= Richard Chirgwin|author-link= Richard Chirgwin|publisher=[[The Register]]|date=2017-05-25|accessdateaccess-date=2017-06-01}}</ref>

==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>{{cite web|url=http://blogs.msdn.com/b/richardb/archive/2007/12/03/vs-2008-and-sourcesafe-q-a.aspx |title=VS 2008 and SourceSafe Q&A - BUGBUG: poor title - Site Home - MSDN Blogs |publisher=Blogs.msdn.com |date=2007-12-03 |accessdateaccess-date=2012-04-13}}</ref> but is not included with Visual Studio Team System 2008.

At the same time, [[Microsoft]] also introduced a source control called [[Team Foundation Version Control]] (TFVC), which was part of project lifecycle management product [[Visual Studio Team System]]. This product addresses many of the shortcomings of Visual SourceSafe, 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 |accessdateaccess-date=2012-04-13}}</ref><ref>{{cite web|url=http://msdn2.microsoft.com/en-us/library/aa302175.aspx |title=Visual SourceSafe Road Map |date=22 March 2011 |publisher=Msdn2.microsoft.com |accessdateaccess-date=2012-04-13}}</ref> There iswas a [hotfix so existing customers could use SourceSafe with Visual Studio 2010.<ref>{{cite web |url=http://code.msdn.microsoft.com/KB976375 hotfix]|title= soKB976375 existing- SourceSafeTFS: customersVSS can use SourceSafeintegration with VisualDev10 Studio|archive-url=https://web.archive.org/web/20100416184257/http://code.msdn.microsoft.com/KB976375 |archive-date=2010.-04-16}}</ref>

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>{{Cite web|url=http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=sourcesafe&Filter=FilterNO|title=Search Product and Services Lifecycle Information - Microsoft Lifecycle}}</ref>

==Further reading==