15 anos atrás a Microsoft tomou a decisão de comprar oque viria a ser tornar um dos mais conhecido software de versionamento de arquivos: O Source Safe, que mais tarde viria a ser tornar Visual Source Safe.

Do nosso site interno (MSW):
November 15, 1994—Microsoft announces the acquisition of One Tree Software, a privately held company based in Raleigh, N.C., and maker of SourceSafe. Laura Yedwab, product unit manager of the Developer Division Repository Group at the time, said, "This spring we went through a 'make versus buy' decision. We did a competitive analysis of all the major versioning and configuration management tools on the market." SourceSafe was the clear winner and replaced Delta in Microsoft's product lineup.
 
One Tree president Brian Harry joined Microsoft after the acquisition. He and his brother Craig are still with the company, based in Raleigh. This week's photo features a shot of the original SourceSafe software recently added to the Archives collection.​

 

Curiosidade para muitos é que internamente os times de produto não usam o Visual Source Safe para gerenciar versionamento de arquivos. Atualmente alguns times estão usando o TFS (Team Foundation Server), porem a grande maioria ainda usa SourceDepot.

No wikipedia em inglês:

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, that very few projects within Microsoft rely on VSS, and that the predominant tool is SourceDepot. According to Matthew Doar

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

Forte abraço.