fix Component Governance file can't find warning #5510
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.
This PR fixes Component Governance warnings that were occurring due to inconsistent capitalization of the configuration parameter across the build system. The warnings showed paths like:
Root Cause
The issue was caused by inconsistent configuration parameter casing:
BuildAll.ps1
defaults to"Release"
(uppercase R)"release"
(lowercase r)build-nupkg.ps1
defaulted to"release"
(lowercase r)This caused
project.assets.json
files to reference different obj directory paths (obj\Release\
vsobj\release\
), creating Component Governance warnings about non-existent paths.