Interested to Buy Any Domain ? << Click Here >> for more details...
If two users check out a project file, how does Visual SourceSafe avoid overwriting changes made by one user when the other user checks in their copy of the file?
- 1 Answers
- 2208 Views
- I also Faced
- E-Mail Answers
Answer / sonakshi
Let us assume that UserA and UserB checked out the same project file, Proj1.vbp. UserA changes the file and checks it in. This will update the file stored in the Visual SourceSafe database. UserB changes their local copy of the file and checks it in. Before updating the server copy, Visual SourceSafe will compare the files in UserB's working folder and the file stored in the Visual SourceSafe database. If UserA and UserB have made different changes to the same parts of the vbp file, Visual SourceSafe will display the Visual Merge window and give UserB the opportunity to specify which changes he or she wants to keep.
| Is This Answer Correct ? | 0 Yes | 0 No |
Is VSS 5.0 compatible with a 4.0 database? Do I have to upgrade all users to the new version? What about 6.0?
How do I recover from a lost administration password?
Using the VSS OLE Automation support in ASP pages?
How to Save a Package as a Separate File?
Is VSS Y2K compliant?
Does VSS 6.0 support NT’s built-in security?
Is there a way to automatically increment/synchronize my project build number and my VSS label/version?
Are there any third party articles which compare VSS with other source code control products?
VSS performance is extremely slow?
How can I use SourceSafe to version stored procedures with Visual Studio 6.0 and SQL Server 7.0?
Tell me is it easy to backup the system?
Is there a way to enable easily switching between multiple source code providers?
VSS 
