Introduction
I was working in a project, and I needed to start a secondary process from an application and pass from the application, the needed parameters and inputs to the secondary process and also capture all possible output and errors from the secondary process. I also did not want the exceptions and crashes from the secondary process to be directly displayed to the user. This article briefly expalins how I achieved this. I had to control the standard input, standard output, and the standard error of the secondary process.
Here is an example of my code in action. The shutdown proces is invoked from my application, and it displays the output from the process. As we did not provide an option or parameter for the secondary process, it captures the standard output and displays it.
I made use of the Process class in System.Diagnostics which can start a process for you. (Most of the people know about this, but they don't relaize the extent to which it can help). I will explain the process in a step by step manner with code snippets so that you can understand it easily.
Using the code
Step 1 : Create a ProcessStartInfo object. This is used to execute the executable. ProcessStartInfo has three constructors. You can use any one of them, or you can specify the file name and argument at a later stage (but before starting the process).
ProcessStartInfo processStartInfo =
new ProcessStartInfo(executableName, executableParameter);
executableName is the full path of the executable. If the executable is placed in a location which is registered in the environment variable, you may omit the full path and specify the executable name. executableParameter is the list of parameters to the executable. The application will be launched with these parameters.
Now, by default, the framework invokes the application using Shell Execute. Set the property UseShellExecute to false.You also need to set the ErrorDialog property to false. So why set the UseShellExecute as false? From the MSDN documentation, you can find that, by default, the shell is used to start the process. Now, to capture the input/output/error, we need to create the process directly from the executable. By doing this, if the application is exposing any input/output/error, we can get in that.
processStartInfo.UseShellExecute = false;
processStartInfo.ErrorDialog = false;
Step 2 : Now, the most important thing comes; we need to set the redirecting properties to true. Set it according to your convenience. However, you can use any other application.
processStartInfo.RedirectStandardError = true;
processStartInfo.RedirectStandardInput = true;
processStartInfo.RedirectStandardOutput = true;
Step 3 : Now that things are done, we are ready to capture the input/output/error. Start the process.
Process process = new Process();
process.StartInfo = processStartInfo;
bool processStarted = process.Start();
Step 4 : Capture the input /output /error streams for your use. Note that the input stream is a writer. For giving input, you need to write the input string in the input stream.
StreamWriter inputWriter = process.StandardInput;
StreamReader outputReader = process.StandardOutput;
StreamReader errorReader = process.StandardError;
process.WaitForExit();
Step 5: You are done; use the streams as needed.
Points of interest
The code is simple enough to understand. But these are the points which can help you to understand the Process.
WaitForExit() function will wait till the application exits. - In the demo application, I have not used the input stream. You can use this as well for giving input to the application.
Process.Start() method returns a bool value which indicates that the process has been started successfully. Process.ExitCode returns an error code returned by the process. If it is 0, the process exited without error. This may be helpful for the users in some scenario. EnableRaisingEvents property enables you to raise the Exited event. So if you want to make use of the Exited event, make sure to assign it to true. ProcessStartInfo.ErrorDialog allows you to set if an error message will be displayed or not if the process is not started successfully. - You can provide a domain name, username, and password for the process in the
ProcessStartInfo object.
ProcessStartInfo.CreateNoWindow allows you to create a process without creating a window.
History
This is the first release of the code. Modifications and feature enhancements will be done on requests. I request users to mail me directly to my email address for any suggestions. In this demo, I have not used the input stream; if you are having trouble with it, then message me and I will provide a sample for that also.
