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
- 2133 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 |
Where can I find some information on Branching/Sharing?
Is there a SourceSafe developers guide?
How can I tell which files in the database correspond to files in my project?
How do I reconnect a project after the shared workspace file loses the project location?
Using the VSS OLE Automation support in ASP pages?
What reporting packages are available for SoucreSafe?
How do I convert my PVCS archive to VSS?
When any person create a new file in the project, he will add it to the Source Control System in the correspoding to folder. This process is called "Checkin". Most of the source control systems provide a windows explorer like user interface. You can checkin files in different ways: 1. Drag and drop files from windows explorer to appropriate folder in source control explorer. 2. Go to appropriate folder in source control system, right click on the folder name and select 'Add Files'. This will launch a file browser which will allow you to select files. 3. Integrate with Visual Studio - most source control systems are integrated with Visual Studio when you install their client software. This is the easiest way to work with source control systems. When you right click on any file in the Solution Explorer in Visual Studio, it will give you the option to checkin or checkout files. After you add (checkin) a file to source control , the file is "controlled" by source control system. If anybody want to change the file (including the person who created the file), he has to "checkout" the file from Source control. When you checkin a file to source control, it will make the file in your computer 'Read only' so that you cannot edit it. This is to remind you that the file is controlled by source control system. You can add new files to source control, but you cannot checkin an existing file unless you have checked out that file.
How to Check Out for Updating?
How to Update Version Control Settings for a Project?
How to require check-in comments?
How do I pin all the files within a project?
VSS 
