SSH: Build task fails on Windows Remotes: ${__process__} does not exist

[xJonathanLEI]

• VSCode Version: 1.40.0-insider (user setup)
• OS Version: Windows_NT x64 10.0.18362

Steps to Reproduce:

1. Establish a Remote Development session to a Windows host

2. Create a new .NET Core project with (I happen to do C# development):

    dotnet new console -o Reproduce
   

3. Open the project folder just created in the Remote Development session

4. Create file .vscode/tasks.json with the following content (the auto-generated stuff):

    {
        "version": "2.0.0",
        "tasks": [
            {
                "label": "build",
                "command": "dotnet",
                "type": "process",
                "args": [
                    "build",
                    "${workspaceFolder}/Reproduce.csproj",
                    "/property:GenerateFullPaths=true",
                    "/consoleloggerparameters:NoSummary"
                ],
                "problemMatcher": "$msCompile"
            }
        ]
    }
   

5. Run the build task

Expected Result:

The build task succeeds as it would natively on the Windows host.

Actual Result:

The build task fails with the following output:

> Executing task: ${__process__} build MY_PATH_TO_PROJECT/Reproduce.csproj /property:GenerateFullPaths=true /consoleloggerparameters:NoSummary <

The terminal shell path "${__process__}" does not exist

Does this issue occur when all extensions are disabled?: N/A

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• TASK: with "args" ,build command error (#79269)
• PATH not loading when running tasks (#82925)
• Wrong value of command property in dotnetBuild taskTemplate (#78976)

[xJonathanLEI]

Maybe not a duplicate of any of those :)

[xJonathanLEI]

Workaround: Change "type":"process" to "type":"shell"

[alexr00]

It looks like the fix I made worked. Can folks who were seeing the issue try again with the latest insiders and confirm?

[xJonathanLEI]

It looks like the fix I made worked. Can folks who were seeing the issue try again with the latest insiders and confirm?

I can confirm the bug has been fixed in the latest insider build :)

[alexr00]

Thank you for verifying!