Need your help in understanding whether 'Microsoft Visual SourceSafe 6.0' is compatible to use on windows 7 64bit OS.If not,what is the alternative product to be chosen in place of 'Microsoft Visual SourceSafe 6.0'. Also could you provide me the URL's from where i can find the details and required for internal audit purpose.
- Visual Studio 6.0 was the last version to include Visual J++, which Microsoft removed as part of a settlement with Sun Microsystems that required Microsoft Internet Explorer not to provide support for the Java virtual machine.
- Mar 25, 2004 Service Pack 6 for Visual Basic 6.0, Visual C++ 6.0 with Visual Source Safe 6.0d provides the latest updates to these products. It is recommended for all users of Visual Basic 6.0, Visual C++ 6.0 and Visual Source Safe 6.0. Visual C++ 6.0 with Visual Source Safe 6.0d from Official Microsoft Download Center. New Surface Pro 6.
- With Visual Studio 2010, Microsoft no longer distributes Visual SourceSafe. Microsoft now offers Team Foundation Server Basic for smaller development teams. There is a hotfix so existing SourceSafe customers can use SourceSafe with Visual Studio 2010.
Developer(s) | Microsoft |
---|---|
Initial release | 1994; 25 years ago |
Stable release | 2005 (8.0.50727.42) / October 2005; 13 years ago |
Operating system | Windows |
Type | Revision control |
License | |
Website | www.microsoft.com |
Microsoft Visual SourceSafe (VSS) is a discontinued source controlprogram, 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.
- 2Overview
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 ManagerGUI), 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]
Accordingly, his self-dubbed 'Helvetica killer' is pitched somewhere in the middle of the two – with a fractionally taller x-height than Helvetica, and slightly squarer edges than Univers. Designed to suit modern typographical needs, without ever sacrificing personality at the altar of practicality (a criticism all-too often levied at Helvetica), FF Bau sports a distinctive double-storey 'g' and a lowercase 'a' that keeps hold of its tail in all available weights. Aktiv grotesk font family arial. FF Bau was designed to suit modern typographical needs without ever sacrificing personality Designed by Christian Schwartz for FontShop International in 2002, this modern alternative to Helvetica has more in common with the Swiss giant's quirkier, warmer 19th century ancestors – such as Akzidenz Grotesk – than with its modern-day incarnation.
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
Version | Date |
---|---|
3.1 | February 14, 1995[10] |
4.0 | September 12, 1995[11] |
5.0 | October 7, 1996[12] |
6.0 | June 3, 1998 [13] |
2005 | January 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[citation needed], VSS appears to be an exception; it is widely rumored[16][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 is now 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.'
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,[20] 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.[21][22] There is a 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.[23]
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
Microsoft Visual Sourcesafe 6.0 Installation
- ↑De Smet, Alan (2009-04-15). 'Visual SourceSafe: Microsoft's Source Destruction System'. Retrieved 2010-09-19.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑Bolton, Michael (2003-01-28). 'Visual SourceSafe Version Control: Unsafe at any Speed?'. Retrieved 2010-09-19.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'Company News; Microsoft Says It Has Acquired One Tree Software'. The New York Times. November 16, 1994. Retrieved 2007-11-21.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'MICROSOFT SHIPS SOURCESAFE SOURCE-CODE-MANAGEMENT SYSTEM'. The Free Library by Farlex. Retrieved 21 May 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'MICROSOFT CORPORATION ACQUIRES ONE TREE SOFTWARE'. The Free Library by Farlex. Retrieved 21 May 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑Gross, Daniel (November 15, 1995). 'Go Configure'. CIO Magazine. Retrieved 21 May 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'Mainsoft to ship Visual SourceSafe for UNIX'. The Free Library by Farlex. Retrieved 21 May 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'Metrowerks Signs Exclusive License for Microsoft Visual SourceSafe on Mac OS'. The Free Library by Farlex. Retrieved 21 May 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'SourceSafe database corruption'. Microsoft. Retrieved 18 Dec 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'MICROSOFT SHIPS SOURCESAFE SOURCE-CODE-MANAGEMENT SYSTEM'. The Free Library by Farlex. Retrieved 21 May 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'MICROSOFT ANNOUNCES VISUAL SOURCESAFE, AN INTUITIVE CODE-MANAGEMENT SYSTEM'. The Free Library by Farlex. Retrieved 21 May 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'Microsoft Announces Visual SourceSafe 5.0,An Intuitive, Project-Oriented Version Control System'. Microsoft. Retrieved 21 May 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'Microsoft Support Lifecycle- Visual SourceSafe 6.0 Standard Edition'. Microsoft Support. Microsoft. Retrieved 21 May 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'Microsoft Support Lifecycle - Visual SourceSafe 2005 Standard Edition'. Microsoft. Retrieved 21 May 2014.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'Best Practices for Preventing Data Corruption'. MSDN.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'Why Not VSS'. Subversionary. Retrieved 2012-04-13.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'It's all Hype. - Jerry Dennany's Occasional Clue'. Weblogs.asp.net. 2003-07-15. Retrieved 2012-04-13.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑Doar, Matthew B. (2005). Practical Development Environments. O'Reilly. p. 73. ISBN0-596-00796-5.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑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. ISBN0-321-86487-5.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'VS 2008 and SourceSafe Q&A - BUGBUG: poor title - Site Home - MSDN Blogs'. Blogs.msdn.com. 2007-12-03. Retrieved 2012-04-13.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑Krill, Paul (2009-09-30). 'Microsoft looks to move SourceSafe users to newer technology | Developer World'. InfoWorld. Retrieved 2012-04-13.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑'Visual SourceSafe Road Map'. Msdn2.microsoft.com. Retrieved 2012-04-13.<templatestyles src='Module:Citation/CS1/styles.css'></templatestyles>
- ↑http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=sourcesafe&Filter=FilterNO
External links
- 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 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[dead link] Source Control and Team Development Using Visual Studio .NET and Visual SourceSafe
Retrieved from 'https://infogalactic.com/w/index.php?title=Microsoft_Visual_SourceSafe&oldid=1811989'