Skip to content

MSBuildDebugEngine env var casing #14705

Description

@jjonescz

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?

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions