One standard issue: the process could be waiting for you to read its output. Create a separate thread to read from its standard output while you’re waiting for it to exit. It’s a bit of a pain, but that may well be the problem.
What is your problem actually? System.Environment.SetEnvironmentVariable changes the environment variables of the current process. If you want to change the variables of a process you create, just use the EnvironmentVariables dictionary property: var startInfo = new ProcessStartInfo(); // Sets RAYPATH variable to “test” // The new process will have RAYPATH variable created with “test” value … Read more
I would recommend stronlgy to go the official route via classes/interfaces in Microsoft.Build namespace. Microsoft uses this all over the place, so this should count for something… Esp. the class Microsoft.Build.Execution.BuildManager and the Singleton Microsoft.Build.Execution.BuildManager.DefaultBuildManager is what you are after to run a build task… source code examples: http://social.msdn.microsoft.com/Forums/en-US/msbuild/thread/ec95c513-f972-45ad-b108-5fcfd27f39bc/ Logging Build messages with MSBuild 4.0
ProcessStartInfo.Verb will only have an effect if the process is started by ShellExecuteEx(). Which requires UseShellExecute = true. Redirecting I/O and hiding the window can only work if the process is started by CreateProcess(). Which requires UseShellExecute = false. Well, that’s why it doesn’t work. Not sure if forbidding to start a hidden process that … Read more
As Hans said, WindowStyle is a recommendation passed to the process, the application can choose to ignore it. CreateNoWindow controls how the console works for the child process, but it doesn’t work alone. CreateNoWindow works in conjunction with UseShellExecute as follows: To run the process without any window: ProcessStartInfo info = new ProcessStartInfo(fileName, arg); info.CreateNoWindow … Read more
You must use ShellExecute. ShellExecute is the only API that knows how to launch Consent.exe in order to elevate. Sample (.NET) Source Code In C#, the way you call ShellExecute is to use Process.Start along with UseShellExecute = true: private void button1_Click(object sender, EventArgs e) { //Public domain; no attribution required. ProcessStartInfo info = new … Read more
This should work. You could try to dump out the contents of the output and error streams in order to find out what’s happening: static void ExecuteCommand(string command) { int exitCode; ProcessStartInfo processInfo; Process process; processInfo = new ProcessStartInfo(“cmd.exe”, “/c ” + command); processInfo.CreateNoWindow = true; processInfo.UseShellExecute = false; // *** Redirect the output *** … Read more
The problem is that if you redirect StandardOutput and/or StandardError the internal buffer can become full. Whatever order you use, there can be a problem: If you wait for the process to exit before reading StandardOutput the process can block trying to write to it, so the process never ends. If you read from StandardOutput … Read more