First, basic debugging: Extract that long command string to a separate var, and print it. 

my $cmdline = 
'C:\windows\system32\WindowsPowerShell\v1.0\powershell.exe -command "&
+ D:\scripts\get-info.ps1 "."\'$val1\' "."\'$filename\'"';

print $cmdline, "\n";

Win32::Process::Create(
    $process,
    $^X,
    $cmdline,
    0,
    DETACHED_PROCESS,
    ".",
);

[download]
You will see that you are not passing the string that you think. When you put a $var in single quotes, it does not get replaced with the value of $var (interpolation). Double-quoted strings *do* interpolate.

Second, (as Anonymous Monk pointed out), $^X is the wrong thing to pass as second parameter; it would run another copy of Perl, instead of PowerShell. Read the docs, not just example code. The Win32::Process docs say that it is the "full path of the executable module", so in your case, it is probably the full path to PowerShell.

When quoting is complex, it helps to build the string in stages, and sometimes to use q{...} and qq{...} in place of '...' and "...".

Use 0 instead of DETACHED_PROCESS until everything else is working right, so you can better see the errors from PowerShell.

The code below is untested for PowerShell, since I lack it on my Win2k box. I don't know exactly what kind of quoting it expects, or what that & does, but this should get you farther down the path: 

use strict;
use warnings;
use Win32::Process;

my $val1     = 'dummy1';
my $filename = 'dummy2';

my $q_val1     = "'" . $val1     . "'";
my $q_filename = "'" . $filename . "'";

my $appname =
    'C:\windows\system32\WindowsPowerShell\v1.0\powershell.exe';

my $ps_command = join ' ', (
    '&',  'D:\scripts\get-info.ps1', $q_val1, $q_filename,
)

my $cmdline = qq{$appname -command "$ps_command"};

print $cmdline, "\n";

my $process;
my $rc = Win32::Process::Create(
    $process,
    $appname,
    $cmdline,
    0,
    0, # replace with DETACHED_PROCESS later
    ".",
);

if ( $rc == 0 ) {
    print Win32::FormatMessage( Win32::GetLastError() );
}
else {
    print "Success!\n";
}

[download]

In reply to Re: How do you pass arguments from Perl to Powershell? by Util
in thread How do you pass arguments from Perl to Powershell? by StangMan71

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.