in reply to VSS automation strange problem

my $result = `SS Dir \"$/\" -Yadmin`;

Have a look at Corion's node where it is pointed out that you didn't do a character escape for the $ in the backticked command. This is likely to take care of the issues you are having. You might notice in my original suggestion I had the command held in a variable ($cmd) which I print out to verify it looks like I want.

    my $cmd = "\"$sspath\\ss.exe\" Checkout \"\$/DMS MW/SCADA/Substati
+on Editor 
+Files/$filename\" -C- -I- -GL\"$checkout_path \"";
    #print "\n********************\n\$cmd=$cmd\n";
    # if the file is already there it doesn't download it again. 
    # BUT, it won't overwrite a file unless the read-only bit is set.

    system $cmd;

[download]

Replies are listed 'Best First'.
Re^2: VSS automation strange problem
by cormanaz (Deacon) on Jan 04, 2017 at 17:01 UTC
    Alas, no help. This 
    #!/usr/bin/perl -w
use strict;
use Cwd;
chdir('C:\Program Files (x86)\Microsoft Visual SourceSafe');
print cwd()."\n\n";
$ENV{SSDIR} = 'C:\Program Files (x86)\Microsoft Visual SourceSafe';
my $env = `echo %SSDIR%`;
print "\n$env\n";
my $cmd = "ss.exe Dir \"\$/\" -Yadmin";
print "$cmd\n\n";
my $result = `$cmd`;
print $result;

    [download]
    yields output 
    C:/Program Files (x86)/Microsoft Visual SourceSafe

C:\Program Files (x86)\Microsoft Visual SourceSafe

ss.exe Dir "$/" -Yadmin

No VSS database (srcsafe.ini) found.  Set the SSDIR environment variab
+le to the path of srcsafe.ini for your VSS database.

    [download]
    "I think computers have complicated lives very bigly. The whole age of, you know, computer has made it where nobody knows exactly what's going on." --D. Trump
[reply]
[d/l]
[select]

      I just tried the code below and it worked. One thing to check is to be sure you're setting SSDIR to where your srcsafe.ini file is located. From the SS GUI you can click the File pulldown menu and in VSS 6.0 anyway it will show you the path to the srcsafe.ini file just above the 'Exit' command. 

      #!/usr/bin/perl
use warnings;
use strict;

my $sspath= 'C:\Program Files (x86)\Microsoft Visual Studio\VSS\win32'
+;

$ENV{SSDIR}="\\\\server\\path-to-ini"; #or local path

#my $cmd = "\"$sspath\\ss.exe\" Dir ";        # listed files in defaul
+t project
my $cmd = "\"$sspath\\ss.exe\" Dir \"\$/\"";  # listed subproject fold
+ers
print "\n********************\n\$cmd=$cmd\n";

system $cmd;

      [download]

      Update: Although you might be providing the path to an ini file already, since you have installed a new version you might have multiple srcsafe.ini files. By checking the path in the GUI you can verify you are using the correct one.

[reply]
[d/l]
[select]
        Sooo....I had put the SSDIR in environment vars via the advanced settings but that didn't fix it. But after a reboot it finally works. Gotta love windoze! Thanks everybody for all the help!
        "I think computers have complicated lives very greatly. The whole age of you know computer has made it where nobody knows exactly what's going on." --D. Trump Indeed.
[reply]

      At least according to the internet, setting the environment variable doesn't always work.

      Have you compared the environment variables that are set when you manually run the command from the command prompt and what %ENV contains?

[reply]
[d/l]

In Section Seekers of Perl Wisdom