VS Code does not use envFile during resolving variables in "program" configuration's property in launch.json.

[shvydd]

A configuration in launch.json:

<!-- Describe the feature you'd like. -->
{
            "name": "Windows MinGW. GDB Launch",
            "type": "cppdbg",
            "request": "launch",
            "cwd": "${workspaceFolder}/build/MinGW/${input:buildType}",
            "envFile": "${workspaceFolder}/build/MinGW/${input:buildType}/bin/.env.vscode",
            "program": "${workspaceFolder}/build/MinGW/${input:buildType}/bin/${CMagneto__ProjectEntrypointExe}",
            ...
}

The .env.vscode (generated dynamically) file defines CMagneto__ProjectEntrypointExe variable.
Idea was to set the binary name in VC Code launch.json from the .env.vscode file.
But VS Code does not use the .env.vscode file during resolving variables in the value of the "program" property. Thus, the launch configuration doesn't work, until ${CMagneto__ProjectEntrypointExe} value is hardcoded in the launch.json file.

I believe, VS Code SHOULD use envFiles during resolving variables of the "program" properties in launch.json.

[connor4312]

envFile is just a property of the debug adapter, not VS Code, and it occurs independent of resolution.

[vs-code-engineering]

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.

Happy Coding!