Isn't it enough for you? Michal Malecki. Hello Jerome, Like we have a lot of projects more than 80 , I would like the people of team A don't see the project of team B in the TeamExplorer. As I far as I know we cannot get it. Please mark the replies as answers if they help and unmark them if they provide no help.
Friday, January 16, AM. Hi Michal, thanks for you answer. I cannot create several severs :- My person in charge of the budget is not agreement with that.
Ok, with team project security settings, I can assign the security access for each project. But apparently I would not have the choice. The results of Analyze can be a little difficult to decipher, but the Administrator help file and also Microsoft KnowledgeBase article Q list the more common errors and documents fixes, where available, for these errors.
After making a backup of the database and attempting to fix it, always run Analyze again to verify that the problem has been fixed, and to find out if fixing this error brought forth any other errors the first problem may have been masking.
In many cases, the Analyze, Backup, Fix cycle may need to be run several times. With the tools available within Windows NT or Windows , it is not difficult to set up a scheduled task to run the Analyze program on a regular basis, and send the results to a text file. From there, you can process the file into your email system, compare it against previous values, or parse it in FoxPro to determine if actions are required. Visual SourceSafe stores the entire tree of source code, as well as the tree structure itself, as a large number of files.
The files are generated with a sequential series of alphabetic names. There are two files with each name, one with no extension, and the second with a ".
A" or ". B" file extension. The file with no extension stores the history of changes to that node in the tree. The file with the extension is the actual contents of that node. If the node is a folder, it contains the folder name and pointers to the files contained in that node. If the node is an actual file a leaf node , the file with an extension contains the source code itself. Each time the file is changed, a new copy of the file is written out, with whichever extension is available. If the write is completed successfully, the original file is deleted.
So, knowing how these obscurely named files match up to the files in your project can give you the ability to recover your source code even if the database was to become severely corrupted. A word of caution: this command appends to an existing file, if it exists. You'll want to delete the existing file if this is not the desired behavior. Figure 3: Results of a Physical File List. Visual SourceSafe lacks an interface to provide you with some key management information.
For example, if you find that your database has grown significantly in size, how to do you determine what caused the size change? Using the physical file list, you can write programs in VFP to help you determine this information:. GO TOP. FOR m. Listing 1: Sample code to parse Physical File List. Microsoft's suggested technique for moving projects between different databases is to use the Archive and Restore options within the SourceSafe Administrator.
The advantage of such a technique is that all history is preserved between databases. However, in many cases, the history is not required.
It is far simpler to perform a "Get Latest Version" on all files from the source database and "Add" all files into the target database.
Also, I have encountered problems with Archive and Restore reporting satisfactory performance, while Analyze reports numerous file problems.
This may have been caused by very old and poorly maintained databases so, if preserving the history is important to you, this avenue is worth a try. After the label is applied, you can specify this label to the SrcSrv indexing script by setting the environment variable, SSLABEL, or by passing it as a command-line parameter, as in the following example:.
Again, this label is required for SrcSrv indexing to work. Note that if you pass a label that does not exist in the project, it can take a long time for the script to complete and the results are of no use. This applies not only at the time the build is indexed, but also on the debugger client. Skip to main content.
This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Submit and view feedback for This product This page. View all page feedback.
0コメント