Fix build #447
Merged
Fix build #447
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.
Fixes #446
Turns out the culprit was a change in behavior of how
<BaseIntermediateOutputPath>is treated with .NET Core SDK 2.1 (not sure exactly what version introduced it). It mangled the intermediate outputs of the various UnitsNet and UnitsNet.Signed builds, causing havoc for its dependent UnitsNet.Serialization.JsonNet and UnitsNet.Serialization.JsonNet.Signed projects.The fix is to use a new special
Directory.Build.propsfile, whose properties are evaluated BEFORE some internal magic in the new build system.The details and workarounds are outlined here:
dotnet/sdk#1518 (comment)