Create a tool and msbuild task to find differences in nuget packages #14460
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.
Creates a command line tool and an msbuild tooltask to find differences in nuget packages. It does a git-style diffing to show line by line differences in the list of files in the package and in the nuspec file. There isn't yet a way to handle expected differences, so the msbuild task always succeeds, but will log any differences it finds.
I'm planning to do more in depth checks on each assembly in the packages and check for each member on each type and take a list of assemblies with expected differences to skip these checks.
Part of dotnet/source-build#4051