Allow the addition of Environment Variables to PowerShell Exe configuration

[rjmholt]

See #1288 (comment) for the proposal.

The suggested form is:

"powershell.powerShellAdditionalExePaths": [
        {
            "versionName": "with-xterm-env-var",
            "exePath": "pwsh",
            "env": {
                "TERM": "xterm"
            }
        }
    ]

This would require some input sanitisation to ensure the environment variables aren't an override...

[rjmholt]

Related to #1470.

[peterblazejewicz]

For anyone interested, this is how we are doing this until env support lands for multi-variable and multi-params:

{
    ...
    "configurations": [
        {
            ...
            "script": "Set-Item -Path Env:VarOneName -Value VarValue; & Set-Item -Path Env:VarTwoName -Value VarValue; & Set-Item -Path Env:VarThreeName -Value VarValue; & ${workspaceFolder}/scripts/build/script.ps1",
            "args": [
                "-ParamOneName ParamValue",
                "-ParamTwoName ParamValue"
            ],
        }
    ]
}

[chuachengling]

Hey there, tried using script, but it seems that script function is not allowed on vscode?

[SadokLadhari]

Any news about this feature please ?

[rjmholt]

Any news about this feature please ?

No news. We're still working through several high priority items in our backlog. This issue is marked as "up for grabs" to indicate that it's free for anyone to pick up and contribute a solution to.

[ggirard07]

Does anyone have a workaround for this while using an interactive session instead of a/current script?