ProcessStartInfo hangs when UseShellExecute = true

Asked Jan 21 '22 at 07:12

Active Jan 21 '22 at 07:15

Viewed 111 times

I was running some exe with ProcessStartInfo

ProcessStartInfo startInfo = new ProcessStartInfo("my.exe");
startInfo.Arguments = "foo.txt bar.txt";
startInfo.WorkingDirectory = path;
Process process = Process.Start(startInfo);
process.WaitForExit();

It was working fine on my PC, but when I move the code to another PC, the same code keep hanging. After some trying, I was able to fix it by setting UseShellExecute to false (and use absolute path for the exe filename).

ProcessStartInfo startInfo = new ProcessStartInfo(Path.Combine(Server.MapPath(@"~\mypath"),"my.exe"));
startInfo.Arguments = "foo.txt bar.txt";
startInfo.UseShellExecute = false;
Process process = Process.Start(startInfo);
process.WaitForExit();

The question is why? Why does using shell hang the process? What is the difference between using or not using shell to execute?

Thanks for the help!

edited Jan 21 '22 at 07:15

ProgrammingLlama

36,677
7
67
86

asked Jan 21 '22 at 07:12

sean

1

Not sure I'd WaitForExit in an ASP.NET context – Caius Jard Jan 21 '22 at 07:15
1

Are you using the same version of .NET? Note that `UseShellExecute`'s default value is true in .NET Framework and false in .NET Core (including .NET 5 and 6). – 41686d6564 stands w. Palestine Jan 21 '22 at 07:17
Does https://stackoverflow.com/questions/5255086/when-do-we-need-to-set-processstartinfo-useshellexecute-to-true answer your question ? – Caius Jard Jan 21 '22 at 07:18
Rather, https://stackoverflow.com/a/68182627/11683. – GSerg Jan 21 '22 at 07:23
@41686d6564 both are .NET framework 4.5.2 Thanks for the links, but they don't seem to answer why my process won't exit. – sean Jan 22 '22 at 13:03

ProcessStartInfo hangs when UseShellExecute = true

0 Answers0