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?

[marcelotmelorax]

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"
            ],
        }
    ]
}

It seems that "args" is ignored when there's a Set-Item in the script. At least it did not work for me, I had to add the args in the end of the script as if I was typing them in the command line. If I don't do like the example below the terminal keeps asking me for values for the mandatory script parameters.

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

[CaseyLaux]

Bumping this to hope it gets seen. Having the same issue now

[andyleejordan]

Hey @CaseyLaux! This is a very old issue, and looking at it, it appears that people are talking about different things. Could you please open a new issue and explain what you're trying to accomplish so we can help you? Thanks!

[ghost]

This issue has been marked as inactive. It has been automatically closed for housekeeping purposes.

[JavaScriptDude]

For the record, this feature request is not moot and should be implemented. The fact that this is auto-closed flags a fundamental issue with issue tracking in general.

I would have this issue flagged as a JDI (just do it) ticket. I used to admin Issue trackers for decades and this idea of JDI was something I implemented for all my enterprise projects. JDI flagged tickets should never be auto closed, and should not be considered in open issue KPIs as they are just common sense stuff, however not high enough priority to get done promptly.

Thanks for your consideration.