Microsoft Visual SourceSafe: Difference between revisions

Revision as of 00:36, 26 October 2021

Revision as of 07:15, 15 February 2022

Line 66:

|}

==Criticism==<big>Big text</big>

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.<ref>{{cite web|url=http://msdn.microsoft.com/en-us/library/ms181079(VS.80).aspx|title=Best PracticeslPractices for Preventing Data Corruption|publisher=MSDN}}</ref> 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==