BUG: "Project History Options" Won't Search for Labels in File (154835)
The information in this article applies to:
- Microsoft Visual SourceSafe, 16-bit, for Windows 4.0
- Microsoft Visual SourceSafe, 16-bit, for Windows 5.0
- Microsoft Visual SourceSafe, 16-bit, for Windows 6.0
- Microsoft Visual SourceSafe, 32-bit, for Windows 4.0
- Microsoft Visual SourceSafe for Windows 5.0
- Microsoft Visual SourceSafe for Windows 6.0
This article was previously published under Q154835 SYMPTOMS
According to the Online Documentation, in the "Project History Options"
dialog box there is a "Labels Only" check box that can be used to search
the current project for any files for a given label.
Specifically, the Online Documentation describes this functionality as
follows:
"Type a time, date, version, or label. Use the prefix D to indicate a
date or time, and the prefix L to indicate a label..."
Attempting to use this dialog box to get a listing of files with a given
label results in a SourceSafe message box that displays:
"There are no items in the list."
After clicking OK on this message box, an empty "Results" window is
displayed.
CAUSE
This function was designed for project searches only.
WORKAROUND
The following SourceSafe command can be used to achieve the desired result:
ss get $/*.* -r -g- -vlmylabel -oresults.txt
The breakdown of the command is as follows:
<ss get>: SourceSafe command to retrieve a read-only output <$/*.*> -
start at project $/, and get all files (hence *.*)
<-r>: recursive - search through all files and sub-projects of
starting project
<-g->: don't actually place read-only files in the working directory
<-vlmylabel>: search for the label "mylabel"
<-oresults.txt>: pipe the results of the search to the named file
At this point, you can look at the results.txt file to see the list of
files that had the label in question assigned to it.
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products
listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 10/15/2002 |
---|
Keywords: | kbBug KB154835 |
---|
|