spawnProcess ignores the workDir argument, but spawnShell does not. I tried with both DMD 2.100.2 and 2.101.0-beta.1, same result. And when I check it in Process Monitor, I can see that the working directory is being accessed at all. But if I switch to using spawnShell, it is.
> And when I check it in Process Monitor, I can see that the working directory is being accessed at all. is *not* being accessed at all
Nevermind, I was just confused by the fact that spawnShell runs the command you give it in workDir. So I expected spawnProcess to do the same.