Microsoft Visual SourceSafe

Last updated
Visual SourceSafe
Original author(s) One Tree Software
Developer(s) Microsoft
Initial release1994;30 years ago (1994)
Final release
2005 (8.0.50727.42) / October 2005;18 years ago (2005-10)
Operating system Windows
Type Version control
License Proprietary commercial software
Website msdn.microsoft.com/de-de/library/ms181038(VS.80).aspx   OOjs UI icon edit-ltr-progressive.svg

Microsoft Visual SourceSafe (VSS) is a discontinued source control 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 [1] [2] to be unstable when used to store large amounts of non-textual data, such as images and compiled executables.

Contents

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, [3] they immediately ceased development on all versions except for Windows. Microsoft SourceSafe 3.1, Windows 16-bit-only and Macintosh, [4] 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. [5] [6] After the acquisition, Mainsoft Corporation developed SourceSafe for UNIX in cooperation with Microsoft. [7] Later, Metrowerks, Inc. developed Visual SourceSafe for Macintosh in cooperation with Microsoft. [8]

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 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 historic bugs in the codebase, occasionally led to SourceSafe database corruption, a problem noted by Microsoft. [9]

Starting with VSS 2005, Microsoft 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.[ citation needed ]

Versions

VersionDate
3.1February 14, 1995 [4]
4.0September 12, 1995 [10]
5.0October 7, 1996 [11]
6.0June 3, 1998 [12]
6.0c (Build 9350)2001 [13]
2005January 27, 2006 [14]

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. [15] 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, [16] VSS appears to be an exception; it is widely rumored [17] that very few projects within Microsoft relied on Visual SourceSafe before the product was discontinued, and that the predominant tool at the time was SourceDepot. According to Matthew Doar: [18]

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, [19] although a VSS transcript[ citation needed ] implied that other large teams use "a mix of customized in-house tools."

Microsoft has since moved on to using Git. [20]

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, [21] 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. [22] [23] There was a hotfix so existing customers could use SourceSafe with Visual Studio 2010. [24]

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. [25]

Further reading

See also

Related Research Articles

<span class="mw-page-title-main">Windows Script Host</span> Automation technology for Windows

The Microsoft Windows Script Host (WSH) is an automation technology for Microsoft Windows operating systems that provides scripting abilities comparable to batch files, but with a wider range of supported features. This tool was first provided on Windows 95 after Build 950a on the installation discs as an optional installation configurable and installable by means of the Control Panel, and then a standard component of Windows 98 and subsequent and Windows NT 4.0 Build 1381 and by means of Service Pack 4. The WSH is also a means of automation for Internet Explorer via the installed WSH engines from IE Version 3.0 onwards; at this time VBScript became means of automation for Microsoft Outlook 97. The WSH is also an optional install provided with a VBScript and JScript engine for Windows CE 3.0 and following and some third-party engines including Rexx and other forms of Basic are also available.

IBM DevOps Code ClearCase (also known as IBM Rational ClearCase) is a family of computer software tools that supports software configuration management (SCM) of source code and other software development assets. It also supports design-data management of electronic design artifacts, thus enabling hardware and software co-development. ClearCase includes revision control and forms the basis for configuration management at large and medium-sized businesses, accommodating projects with hundreds or thousands of developers. It is developed by IBM.

Remote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft Corporation which provides a user with a graphical interface to connect to another computer over a network connection. The user employs RDP client software for this purpose, while the other computer must run RDP server software.

<span class="mw-page-title-main">Shadow Copy</span> Microsoft technology for storage snapshots

Shadow Copy is a technology included in Microsoft Windows that can create backup copies or snapshots of computer files or volumes, even when they are in use. It is implemented as a Windows service called the Volume Shadow Copy service. A software VSS provider service is also included as part of Windows to be used by Windows applications. Shadow Copy technology requires either the Windows NTFS or ReFS filesystems in order to create and store shadow copies. Shadow Copies can be created on local and external volumes by any Windows component that uses this technology, such as when creating a scheduled Windows Backup or automatic System Restore point.

Microsoft Servers is a discontinued brand that encompasses Microsoft software products for server computers. This includes the Windows Server editions of the Microsoft Windows operating system, as well as products targeted at the wider business market. Microsoft has since replaced this brand with Microsoft Azure, Microsoft 365 and Windows 365.

<span class="mw-page-title-main">Git</span> Distributed version control software system

Git is a distributed version control system that tracks versions of files. It is often used to control source code by programmers who are developing software collaboratively.

Microsoft SQL Server Express is a version of Microsoft's SQL Server relational database management system that is free to download, distribute and use. It comprises a database specifically targeted for embedded and smaller-scale applications. The product traces its roots to the Microsoft Database Engine (MSDE) product, which was shipped with SQL Server 2000. The "Express" branding has been used since the release of SQL Server 2005.

Microsoft Forefront is a discontinued family of line-of-business security software by Microsoft Corporation. Microsoft Forefront products are designed to help protect computer networks, network servers and individual devices. As of 2015, the only actively developed Forefront product is Forefront Identity Manager.

Vault is a commercial, proprietary version control system by SourceGear LLC which markets its product as a replacement for Microsoft's Visual Source Safe.

<span class="mw-page-title-main">Windows Home Server</span> Home server operating system by Microsoft released in 2007

Windows Home Server is a home server operating system from Microsoft. It was announced on 7 January 2007 at the Consumer Electronics Show by Bill Gates, released to manufacturing on 16 July 2007 and officially released on 4 November 2007.

Microsoft Application Virtualization is an application virtualization and application streaming solution from Microsoft. It was originally developed by Softricity, a company based in Boston, Massachusetts, acquired by Microsoft on July 17, 2006. App-V represents Microsoft's entry to the application virtualization market, alongside their other virtualization technologies such as Hyper-V, Microsoft User Environment Virtualization (UE-V), Remote Desktop Services, and System Center Virtual Machine Manager.

Azure DevOps Server, formerly known as Team Foundation Server (TFS) and Visual Studio Team System (VSTS), is a Microsoft product that provides version control, reporting, requirements management, project management, automated builds, testing and release management capabilities. It covers the entire application lifecycle and enables DevOps capabilities. Azure DevOps can be used as a back-end to numerous integrated development environments (IDEs) but is tailored for Microsoft Visual Studio and Eclipse on all platforms.

Aldon is a business unit of Rocket Software. It develops, manufactures, licenses and supports software change management products for the enterprise application lifecycle management (ALM) and software change management (SCM) markets.

<span class="mw-page-title-main">Visual Studio</span> Code editor and IDE

Visual Studio is an integrated development environment (IDE) developed by Microsoft. It is used to develop computer programs including websites, web apps, web services and mobile apps. Visual Studio uses Microsoft software development platforms including Windows API, Windows Forms, Windows Presentation Foundation (WPF), Microsoft Store and Microsoft Silverlight. It can produce both native code and managed code.

<span class="mw-page-title-main">Windows Server 2008 R2</span> Fifth version of Windows Server, released in 2009

Windows Server 2008 R2, codenamed "Windows Server 7", is the ninth version of the Windows Server operating system produced by Microsoft and released as part of the Windows NT family of operating systems. It was released to manufacturing on July 22, 2009, and became generally available on October 22, 2009, the same respective release dates of Windows 7. It is the successor to Windows Server 2008, which is derived from the Windows Vista codebase, released the previous year, and was succeeded by the Windows 8-based Windows Server 2012.

Unity Version Control is a cross-platform commercial distributed version control tool developed by Códice Software for Microsoft Windows, Mac OS X, Linux, and other operating systems. It includes a command-line tool, native GUIs, diff and merge tool and integration with a number of IDEs. It is a full version control stack not based on Git.

Attack Surface Analyzer is a tool created for the analysis of changes made to the attack surface of the operating systems since Windows Vista and beyond. It is a tool recommended by Microsoft in its SDL guidelines in the verification stage of the development.

Surround SCM is a software configuration management application developed by Seapine Software, now owned by Perforce since 2017. Perforce integrated the software with its Helix ALM product.

The history of Microsoft SQL Server begins with the first Microsoft SQL Server database product – SQL Server v1.0, a 16-bit relational database for the OS/2 operating system, released in 1989.

References

  1. ↑ De Smet, Alan (2009-04-15). "Visual SourceSafe: Microsoft's Source Destruction System" . Retrieved 2010-09-19.
  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. 1 2 "MICROSOFT SHIPS SOURCESAFE SOURCE-CODE-MANAGEMENT SYSTEM". The Free Library by Farlex. Retrieved 21 May 2014.
  5. ↑ "MICROSOFT CORPORATION ACQUIRES ONE TREE SOFTWARE". The Free Library by Farlex. Retrieved 21 May 2014.
  6. ↑ Gross, Daniel (November 15, 1995). "Go Configure". CIO Magazine. Retrieved 21 May 2014.
  7. ↑ "Mainsoft to ship Visual SourceSafe for UNIX". The Free Library by Farlex. Retrieved 21 May 2014.
  8. ↑ "Metrowerks Signs Exclusive License for Microsoft Visual SourceSafe on Mac OS". The Free Library by Farlex. Retrieved 21 May 2014.
  9. ↑ "SourceSafe database corruption". Microsoft. Retrieved 18 Dec 2014.
  10. ↑ "MICROSOFT ANNOUNCES VISUAL SOURCESAFE, AN INTUITIVE CODE-MANAGEMENT SYSTEM". The Free Library by Farlex. Archived from the original on 2014-05-21. Retrieved 21 May 2014.
  11. ↑ "Microsoft Announces Visual SourceSafe 5.0, An Intuitive, Project-Oriented Version Control System". Microsoft. Archived from the original on 2014-06-10. Retrieved 21 May 2014.
  12. ↑ "Microsoft Support Lifecycle- Visual SourceSafe 6.0 Standard Edition". Microsoft Support. Microsoft. Retrieved 21 May 2014.
  13. ↑ Microsoft Corporation (2001). "Visual SourceSafe 6.0c Readme" (Readmess.htm). Microsoft Visual SourceSafe 6.0c [CD-ROM].
  14. ↑ "Microsoft Support Lifecycle - Visual SourceSafe 2005 Standard Edition". Microsoft. Retrieved 21 May 2014.
  15. ↑ "Best Practices for Preventing Data Corruption". MSDN.
  16. ↑ "Microsoft tests its own dog food". ZDNet . CBS Interactive. July 21, 2003. Archived from the original on January 8, 2007. Retrieved October 9, 2005.
  17. ↑ "It's all Hype. - Jerry Dennany's Occasional Clue". Weblogs.asp.net. 2003-07-15. Retrieved 2012-04-13.
  18. ↑ Doar, Matthew B. (2005). Practical Development Environments. O'Reilly. p. 73. ISBN   0-596-00796-5.
  19. ↑ Guckenheimer, Sam; Neno Loje (2012). Visual Studio Team Foundation Server 2012: Adopting Agile Software Practices: From Backlog to Continuous Feedback (3rd Edition) (Microsoft Windows Development Series). O'Reilly. p. 241. ISBN   978-0-321-86487-1.
  20. ↑ Richard Chirgwin (2017-05-25). "Windows is now built on Git, but Microsoft has found some bottlenecks". The Register . Retrieved 2017-06-01.
  21. ↑ "VS 2008 and SourceSafe Q&A - BUGBUG: poor title - Site Home - MSDN Blogs". Blogs.msdn.com. 2007-12-03. Retrieved 2012-04-13.
  22. ↑ Krill, Paul (2009-09-30). "Microsoft looks to move SourceSafe users to newer technology | Developer World". InfoWorld. Retrieved 2012-04-13.
  23. ↑ "Visual SourceSafe Road Map". Msdn2.microsoft.com. 22 March 2011. Retrieved 2012-04-13.
  24. ↑ "KB976375 - TFS: VSS integration with Dev10". Archived from the original on 2010-04-16.
  25. ↑ "Search Product and Services Lifecycle Information - Microsoft Lifecycle".
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.