2

So I have a chunk of code to call powercfg with the /requests option and get the result back from stdout.

Process p = new Process();
p.StartInfo.UseShellExecute = false;
p.StartInfo.RedirectStandardOutput = true;
p.StartInfo.FileName = "powercfg";
p.StartInfo.Arguments = "/requests";
p.Start();

string output = p.StandardOutput.ReadToEnd();
p.WaitForExit();

However when I run this code I get entirely different output than when I run the same command on the command line.

In the case of the code version I only get a load of "[DRIVER] ?" values back, but on the command line I get usually 2 or 3 properly formed responses.

I've run my code from the same command prompt window as the same user with the same environment, still no joy.

Any ideas ?

Eva No Gainen
  • 65
  • 1
  • 6

2 Answers2

1

So the actual reason was that my application needed to be compiled for "Any CPU". Setting it to x86 or x64 caused issues with it loading the correct version of one of the dependent libraries.

Eva No Gainen
  • 65
  • 1
  • 6
0

It may have something to do with the user context your application is running in, for example if you run your app as an administrator Process.Start will attempt to start the process in the same context.

animaonline
  • 3,715
  • 5
  • 30
  • 57
  • Well I did consider that, that's why I ran my program in the same shell as the command on it's own... one after another... surely that means they both use the same user context ? – Eva No Gainen Feb 20 '13 at 14:20