Support passing environment variables to processes

[damianh]

Use case(s)

Some of our tooling (basically around yarn / npm) leverages environment variables instead of arguments and some scenarios it not possible to pass args via scripts nested in package.json. (How does software even work?)

Description

Since simple-exec is a wrapper around ProcessStartInfo which already supports EnviromentVariables and since UseShellExecute is false, it should allow the caller to optionally modify before executing:

public static void Run(string name, ..snip... , Action<IDictionary<string, string>> configEnvironmentVariables = null);

Example usage:

Run("foo", ...snip..., env => env["bar"] = "baz");

Alternatives

This is nasty yo

Environment.SetEnvironmentVariable("bar", "baz"); 
RunCmd("yarn", "somescript");
Environment.SetEnvironmentVariable("", ""); 

Additional context

None.

[adamralph]

I like it! And I could use it to simplify the MinVer package tests.

[adamralph]

@damianh I've released this in 6.2.0-rc.1. Can you take it for a spin?

[damianh]

I will

[adamralph]

I'm doing so too. And loving it!

• https://github.com/adamralph/liteguard/pull/312/files#diff-29155d6173e232402371c24c8b206e60R21
• https://github.com/xbehave/xbehave.net/pull/639/files#diff-29155d6173e232402371c24c8b206e60R21

[damianh]

Works here 👍