Search results for query: *

I had the same problem. The work around I came up with was as follows: Batch file 1 - Essentially has a line for every folder in sourcesafe. I know this is tedious but you only have to do it once and add a line for every new folder you create. Every line has a call to Batch file 2 passing in...

You can't rollback in groups because SourceSafe doesn't take the assumption that all files are on the same version number. i.e. Version 10 on file A may not be the same as Version 10 on file B

I did the same thing with batch files...try this Try this: ss get %SSPATH%/*.* -GL%Destination% -R- -I-Y Replace %SSPATH% with your sourcesafe path and replace %Destination% with your desired location for the files.

Someone with the proper rights can Undo the check out essentialy reverting it to the state before the check out.

No that I'm aware of. The command line ss.exe is made to be inclusive of the actual VSS GUI functionality and not the VSS Admin GUI. If you could list them you wouldnt need to put in such system variables such as SSUSER and SSPWD.

It is possible to pin whole folders and multiple files but it has to be done through the command line. The VSS GUI isn't inclusive of all the command line features. Here is a link with the pinning command line syntax...

Is there a way to search by label or to have a get done from a packing list? I'm trying to institute a release based source code control and trying to figure out a way to be able to search which files have changed through the label. If this isn't plausible, what about using the command line...