Fix casing of Properties directory in updateAssemblyInfo.ps1 script #2189
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When attempting to invoke the updateAssemblyInfo.ps1 script from a Linux environment using PowerShell Core, it gets errors because the assembly info paths that are generated do not exist. This is because the generated path uses lowercase
propertiesinstead of the actual name that exists on disk:Properties. Unlike Windows, Linux file system is case-sensitive. This is fixed by using the correct casing.This change is necessary to support .NET's source-build which builds this repo (see dotnet/source-build#3565).