Add option to control inheriting pre-build steps #114
Conversation
This file contains hidden or 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
- Added InheritBuildSteps to control taking build steps from child projects - Allow build order only exe dependencies for lib projects. This is useful for making sure a tool is build before running the build (thinking custom build step here)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
By default pre-build steps of a dependency end up in the final project that added them as a dependency. I'm not sure if this is the intended behavior or not. This change adds:
DependencySettingenum.Not sure if this code can be taken seeing as the pre build step default behavior might be wrong anyways. This is the fix I came up with which might drive a more complete fix.