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?
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 |
Using the VSS OLE Automation support in ASP pages?
How to Update Version Control Settings for a Project?
Are there any third party articles which compare VSS with other source code control products?
Are the any windows shell extensions for SourceSafe?
How can I move a database or create a new one?
Which is the best product for source controlling compair to VSS for vesion controlling
Is there an API for VSS? Where can I get it?
Can I use VSS on Unix or Mac systems?
How can I automate database maintenance routines?
Where can I find the SSSCC API?
How do I display a custom message box during Add Item, Check In, Ckeck Out, Undo Checkout, Branch, and Rename?
How do I get deleted files (not permanently deleted)?