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
- 1694 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 |
How can I tell which files in the database correspond to files in my project?
How to Create a New Shared CaseComplete Project?
The integration isn’t working between VSS and FrontPage/Visual InterDev. What can I do?
How to Structure and Partition your Project?
How do I convert my PVCS archive to VSS?
What are Package Files?
Is there a way to automatically increment/synchronize my project build number and my VSS label/version?
How can I get around the synchronization issue such that deletes and renames from VS.NET do not get synchronize with VSS as described in Q305516?
Is there an issue/bug tracking tool that integrates with SourceSafe?
What is Multiple Checkout?
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?
Is there a SourceSafe developers guide?
VSS 
