Correct props file path case #1637
Merged
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
SpecFlow.Tools.MsBuild.Generation.props used a different casing to reference the Buildsystem folder than is present in the package. This seems like the smallest change to correct an out of the box failure utilising the MsBuild generation on linux.
|
Thanks for your contribution to SpecFlow. If you would like us to send you some SpecFlow stickers as a thank you, please fill out the form here. |
idg10
pushed a commit
to idg10/SpecFlow
that referenced
this pull request
Jan 8, 2020
SpecFlow.Tools.MsBuild.Generation.props used a different casing to reference the Buildsystem folder than is present in the package. This seems like the smallest change to correct an out of the box failure utilising the MsBuild generation on linux.
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.
SpecFlow.Tools.MsBuild.Generation.props used a different casing to reference the Buildsystem folder than is present in the package. This seems like the smallest change to correct an out of the box failure utilising the MsBuild generation on linux. Is nobody using SpecFlow on linux or macOS at the moment? Anyway this fix isn't a code change and the casing of a path should have no effect on Windows users.
Types of changes
Checklist: