Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We have seen issues on the Arm64 platform arising from differences in capitalization, including long build times due to redundant build targets (arm64 vs ARM64). Because VC++ explicitly wants upper case (ARM64) whereas .NET doesn't care outside of runtime identifiers and Nuget architecture, upper case is what was chosen (the aforementioned exceptions are explicitly lower-cased in the handful of places where they are relevant).
Our recommendation for best practice is:
Motivation and Context
The root cause is that our build was using inconsistent casing for the platform name (arm64 vs ARM64) which caused MSBuild to not recognize when multiple requested builds were building the same project with the same configuration and thus spawn multiple processes resulting in file access conflicts.
How Has This Been Tested?
Smoke testing
Types of changes