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.

Roboticus

Thanks again, looks good