You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 14, 2020. It is now read-only.
It seems like nuget 4.9.3 (which gets used by Visual Studio 15.9) changed the way that NuGetAssetsLock.props files are generated.
In earlier versions of nuget (e.g., 4.6.2) the Sha512 embedded in the NugetAssetLock.props file comes from the package's .nupkg.sha512.
In 4.9.3, the Sha512 comes from the .nupkg.metadata file, specifically from a json field in it called contenthash.
As a result, anyone building in Visual Studio 15.9 and/or who updates their build\local\nuget binary to 4.9.3 will always generate asset lock files that fail package validation.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It seems like nuget 4.9.3 (which gets used by Visual Studio 15.9) changed the way that NuGetAssetsLock.props files are generated.
In earlier versions of nuget (e.g., 4.6.2) the Sha512 embedded in the NugetAssetLock.props file comes from the package's .nupkg.sha512.
In 4.9.3, the Sha512 comes from the .nupkg.metadata file, specifically from a json field in it called contenthash.
As a result, anyone building in Visual Studio 15.9 and/or who updates their build\local\nuget binary to 4.9.3 will always generate asset lock files that fail package validation.
The text was updated successfully, but these errors were encountered: