Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate Newtonsoft.Json version matches VS/.NET Core SDK version #2880

Merged
merged 1 commit into from
Jun 11, 2019

Conversation

zivkan
Copy link
Member

@zivkan zivkan commented Jun 8, 2019

Bug

Fixes: NuGet/Home#8108
Regression: No

  • Last working version:
  • How are we preventing it in future:

Fix

Details: MSBuild target to run after restore to ensure that resolved version of Newtonsoft.Json matches the version in our config.props file.

I had to add a bunch of PackageReferences with NoWarn="NU1605". If NuGet/Home#5740 gets implemented, many of these may no longer be needed.

Testing/Validation

Tests Added: No
Reason for not adding tests: no product changes,
Validation: run build.ps1

@zivkan zivkan force-pushed the dev-zivkan-ValidateNewtonsoftJsonVersion branch 3 times, most recently from 188d8e0 to 2add553 Compare June 8, 2019 18:03
Copy link
Member

@nkolev92 nkolev92 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are absolutely all the references needed?

Basically will every & any line revert cause a potential problem, or will 9.0.1 be selected?

@zivkan
Copy link
Member Author

zivkan commented Jun 11, 2019

I think only 2 or 3 projects needed the reference to change the version of Newtonsoft.Json. All the others were only to stop the NU1605 warnings that are promoted to errors and therefore break the build. I didn't want to supress all NU1605 warnings, only for Newtonsoft.Json.

Copy link
Member

@nkolev92 nkolev92 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense.
It's the transitive no warn issue (which has no easy solution).

@zivkan zivkan force-pushed the dev-zivkan-ValidateNewtonsoftJsonVersion branch from 2add553 to eb50688 Compare June 11, 2019 17:20
@zivkan zivkan merged commit 117c4bd into dev Jun 11, 2019
@zivkan zivkan deleted the dev-zivkan-ValidateNewtonsoftJsonVersion branch June 11, 2019 20:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ensure all projects use the same version of Newtonsoft.Json
3 participants