Kevin Dente's Blog

The Blip in the Noise
Visual SourceSafe - recursive handling bug from command line

In case anyone else bangs their head against this – in SourceSafe, there seems to be a bug in recursive file handling using the command line tools. I tried performing a recursive checkout using a specific filename (AssemblyInfo.cs, in this case), but SourceSafe claimed to not find any matching files. However, if I specify a wildcard character (AssemblyInfo*.cs), it works as expected (although it wouldn’t be exactly the right behavior if I had an AssemblyInfo2.cs file). In other words, this:

ss checkout -R AssemblyInfo.cs

does not work, but this:

ss checkout -R AssemblyInfo*.cs

does.

 It appears that the recursive behavior requires a wildcard character to work correctly.

 

 

Published Monday, July 31, 2006 8:25 PM by kevindente

Filed under:

Comments

# re: Visual SourceSafe - recursive handling bug from command line@ Monday, September 04, 2006 10:56 PM

Why are you still using SourceSafe?

Mark

# re: Visual SourceSafe - recursive handling bug from command line@ Monday, September 04, 2006 11:07 PM

Not by my choice, believe me.

kevindente

# re: Visual SourceSafe - recursive handling bug from command line@ Friday, December 21, 2007 4:27 PM

If by coincidence or design you have an AssemblyInfo.cs in the directory you're running SourceSafe from, the default behavior is to try to recurse down *from AssemblyInfo.cs*, not the curdir. Which fails, because unless you work REALLY REALLY HARD a file is not a directory. Adding a wildcard causes it to start from the curdir.

Andrew Cook

Leave a Comment

(required) 
(required) 
(optional)
(required)