Repro steps:
- Be on Linux. The behavior is different there.
- Create a folder with a space in the name
- Go into that folder,
dotnet new mvc
- Open VSCode to that folder
- Debug in container (by doing SDK or by adding Dockerfiles first)
- The container starts but VSDBG in the container fails to launch the app executable
I suspect the right fix is to use our commandLineBuilder tech in here:
|
args: debugConfiguration.args || [additionalProbingPathsArgs, containerAppOutput].join(' '), |
As far as I can tell, the coreclr launch configuration does accept a string array of args instead of a flat string. However, we would need to rewrite a few things, namely:
|
private static getAdditionalProbingPathsArgs(platformOS: PlatformOS): string { |
|
const additionalProbingPaths = platformOS === 'Windows' |
|
? [ |
|
'C:\\.nuget\\packages', |
|
'C:\\.nuget\\fallbackpackages' |
|
] |
|
: [ |
|
'/root/.nuget/packages', |
|
'/root/.nuget/fallbackpackages' |
|
]; |
|
return additionalProbingPaths.map(probingPath => `--additionalProbingPath ${probingPath}`).join(' '); |
|
} |
Repro steps:
dotnet new mvcI suspect the right fix is to use our
commandLineBuildertech in here:vscode-containers/src/debugging/netcore/NetCoreDebugHelper.ts
Line 118 in 2159513
As far as I can tell, the
coreclrlaunch configuration does accept a string array ofargsinstead of a flat string. However, we would need to rewrite a few things, namely:vscode-containers/src/debugging/netcore/NetCoreDebugHelper.ts
Lines 261 to 272 in 2159513