Interested to Buy Any Domain ? << Click Here >> for more details...
Where is the main copy of the Visual Basic project stored?
- 1 Answers
- 2424 Views
- I also Faced
- E-Mail Answers
Answer / sonakshi
The main copy of the project is located in the Visual SourceSafe database. After modifying their local copies, all users should check the files into Visual SourceSafe. This will cause the latest version of the user's work to be stored in Visual SourceSafe. Every time you open the Visual Basic project, Visual Basic will use the information in the local Mssccprj.scc file to retrieve the latest version of the files from Visual SourceSafe and replace the local copies of the user's Visual Basic files.
| Is This Answer Correct ? | 0 Yes | 0 No |
How do I reconnect a Visual C++ project after I have branched or shared it to a new location?
How do I apply a label to an older version of a file?
Tell me can database be accessed without sharing the folder?
Is there a SourceSafe developers guide?
How can I lock and unlock the VSS database prior to running Analyze or backing up the database?
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.
What is Exclusive Checkout?
Is VSS Y2K compliant?
How do I get deleted files (not permanently deleted)?
VSS performance is extremely slow?
Does VSS OLE Automation support pinning?
Does VSS OLE Automation support label comments?
VSS 
