Knowledge Base

BUG: Recursive History Fails if Used With -f- Switch

Article ID: 193585

Article Last Modified on 3/10/2005

Microsoft Visual SourceSafe 5.0 Standard Edition
Microsoft Visual SourceSafe 6.0 Standard Edition

This article was previously published under Q193585

SYMPTOMS

When the SourceSafe History command is used on a project with the -r (recursive) and -f- (Do Not Display Individual File Updates) switches, the -r switch does not work correctly.

CAUSE

This problem only occurs when using the -r and -f- switches together.

RESOLUTION

Use the SourceSafe Explorer to generate a recursive project history that does not show file updates.

To accomplish this, clear the "Include file checkins" option in the Project History Options dialog box.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce Behavior

From the SourceSafe Explorer:

Create a project named TestProj under $/, then add a subproject named SubProj under TestProj.
Add some files to the TestProj and SubProj projects. Next, check out, modify, and check in the files to create some history for the files.

From the Command Line:

Set the current database with the following command:

     set ssdir = <path to SourceSafe directory>

Get the history for the project, $/TestProj in addition to the subprojects for $/TestProj with the following command:
```
      ss history -r -f- $/TestProj
						
```

Notice that only the files contained in $/TestProj are listed instead of the files in both the $/TestProj and $/TestProj/SubProj directories.

REFERENCES

For additional information, please see the following article in the Microsoft Knowledge Base:

128723 HOWTO: Reference a Time on the Command Line

Visual SourceSafe Books Online; search on: "History"

Additional query words: kbDSupport sub

Keywords: kbbug kbcommandline kbpending KB193585