title: Trouble launching program with System.Diagnostics.Process.Start()
body: <p>What should be a <em>trival</em> matter has now gobbled up an hour of my time! >__&lt;</p>
  
  <p>I want to start an executable with a xml path as an argument.  (I've added the directory in which this program resides to my system path.)  Seems simple enough. My first approach was using the static Process.Start() method as such: </p>
  
  <p><code>
  Process.Start(@"MyExecutable.exe", "C:\\My Doc\\SomeDirectory\\MyXMLPath.xml");
  </code> </p>
  
  <p>The process does start, but like half a second later it dies. So, I'm like <em>ooookaay</em>, maybe the executable doesn't like the argument I'm giving it?  Just for giggles, I created a shortcut to the executable and added the xml file path as one of it's arguments.  The program starts and runs as expected.  Not sure why this works, I decided to test my luck on the command line as well:</p>
  
  <p><code>
  C:\MyExecutable.exe "C:\My Docs\SomeDirectory\MyXMLPath.xml"
  </code>   </p>
  
  <p>No problem starting this way too.</p>
  
  <p>Now, at this point I started grasping for straws and decided to create an instance of the Process class:</p>
  
  <pre>
  Process proc = new Process();
  proc.StartInfo.FileName = @"MyExecutable.exe";
  proc.StartInfo.Arguments = "C:\\My Docs\\SomeDirectory\\MyXMLPath.xml";
  proc.Start();
  </pre>
  
  <p>Needless to say this didn't help at all. >.&lt;</p>
  
  <p>So frusterated, I decided test my luck commenting out one line:</p>
  
  <p><code>
  //proc.StartInfo.Arguments = "C:\\My Docs\\SomeDirectory\\MyXMLPath.xml";
  </code></p>
  
  <p>And the process starts. Not with its necessary arguments, but it starts. So, the question is, why is the program not accepting the path I give it when I try to launch it through the Process class?  If only it left me a message when the program died. :( </p>
  
  <p>Any thoughts? Much appreciated! </p>