This repository has been archived by the owner on Feb 8, 2022. It is now read-only.
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.
NuGet 4.9 enabled repeatable package restores using a lock file. A sha512 of the content is used so a nuget package returns the same hash before it is signed and after. Unfortunately, the contentHash is giving different results on different platforms. and nuget packages with the same version, but different sdk versions are resulting in different contentHash values.
Working lock files are required to have deterministic builds. I'd really like to see deterministic builds become common in our .NET community. I would also like to see these contributions reviewed and merged:
NuGet: allow creating deterministic packages
NuGet/NuGet.Client#2775
Add support for --pathmap
dotnet/fsharp#5801
add deterministic to msbuild targets
dotnet/fsharp#6363