In both perl and C#, the simple "pass a command-line string" version of starting a command actually fires up a command shell which breaks the line up into pieces in order to actually start the process. Since you already have the pieces ahead of time, you can avoid that overhead by starting up the process with the argument list already separate:

// C#
using System.Diagnostics;

class MyProgram {
    static void Main(string[] args) {
        string MyExe = "C:\path\to\perl.exe";
        string MyScript = args[0];
        string MyDir = "Test Dir";
        
    Process.Start(MyExe, MyScript, MyDir);
    }
}

# Perl
my ($MyExe, $MyDir) = ("C:/path/to/perl.exe", "Test Dir");
my $MyScript = shift;
system($MyExe, $MyScript, $MyDir);

[download]

If you use the ProcessStartInfo structure to configure your process before you start it, you can do nice things like capture the output stream(s), set up the environment variables, etc.

Update: the description of process startup is deliberately simplified, the actual process is a bit smarter than that.

...roboticus

When your only tool is a hammer, all problems look like your thumb.

In reply to Re^3: Dealing with spaces in folder names with ARGV[0] by roboticus
in thread Dealing with spaces in folder names with ARGV[0] by Anonymous Monk

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.