error when access timeout for process

Question

1.00/5 (1 vote)

See more:

Hello
I have this method to execute commands

private static int ExecuteCommand(string command, int timeout)
       {
           var processInfo = new ProcessStartInfo("cmd.exe", "/C " + command)
           {
               CreateNoWindow = true,
               UseShellExecute = false,
               WorkingDirectory = "C:\\",
           };

           var process = Process.Start(processInfo);
           process.WaitForExit(timeout);
           var exitCode = process.ExitCode;
           process.Close();

           return exitCode;
       }

some times i get an exception in

var exitCode = process.ExitCode;

the exception is:

Process must exit before requested information can be determined.

Posted 27-Jul-15 10:52am

M. Daban

Add a Solution

Comments

Sergey Alexandrovich Kryukov 27-Jul-15 17:18pm

This is not "access timeout"; such expression does not make much sense.
—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2015-07-27T11:17:00

All right, very nice. But it means you don't need this process.ExitCode value, because it makes no sense at the moment of the call. What's wrong with that? You can use this very condition, the fact of having this exception, to tell the state of the process: sandwich this property call in try-catch block and see if you have this exception. :-)

More seriously, you can do it by checking process.HasExited in advance: https://msdn.microsoft.com/en-us/library/system.diagnostics.process.hasexited%28v=vs.110%29.aspx[^].

You see, you call process.WaitForExit(timeout); is apparently a blocking call. It puts the calling thread in a wait state: the system switches out your thread and does not schedule it back to execution until it is waken up, it wastes no CPU time for the wait. The thread can be waken up by a number of reasons, and one of them is timeout. So, when the execution goes past to the call, you don't know exact reason of waking up. You can find it out by checking up the process status.

By the way, in interactive UI applications it would be the reason to execute such things in a separate thread, not a UI thread.

—SA