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.
It turns out, that Visual Studio really don't like having most of the pathVars in the
<Outputs>
property of a custom build command....this just doesn't work. The command does the right thing, but the tracking of the outputs goes wrong, and visual studio manages to actually create a
$(SolutionDir)
folder on disk too.So instead of making pathVars the default for buildoutputs and buildinputs, we turn it off, and only turn it on through an override in the environment where appropriate.