It looks like MSBuildDebugEngine is accepted in that exact casing which matters on Unix where env vars are case-sensitive. Unfortunately, Azure DevOps automatically upper-cases global variables when passing them as env vars, so it's impossible to have
variables:
- name: MSBuildDebugEngine
value: 1
- name: MSBUILDDEBUGPATH
value: $(Build.ArtifactStagingDirectory)/binlogs
without also adding
env:
MSBuildDebugEngine: $(MSBuildDebugEngine)
to every step in Unix pipelines.
Would it be possible to accept the upper-cased MSBUILDDEBUGENGINE on Unix too?
It looks like
MSBuildDebugEngineis accepted in that exact casing which matters on Unix where env vars are case-sensitive. Unfortunately, Azure DevOps automatically upper-cases global variables when passing them as env vars, so it's impossible to havewithout also adding
to every step in Unix pipelines.
Would it be possible to accept the upper-cased
MSBUILDDEBUGENGINEon Unix too?