Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
1.7.1 - limit on Newtonsoft.Json version
See original GitHub issueI am wondering what the reason behind adding a hard stop on the nuget Newtonsoft.Json dependency e.g. [7,8)
From what I can tell, there are some minor breaking changes between the versions but NEST does not use these and continues to work with v8 with an assembly redirect. The upper limit is causing a number of issues when updating nuget packages (We are using 1 of the new v8 features - ArrayPool support).
Can this nuspec dependency version specification be diluted to perhaps [7,9) - assuming I haven’t missed any broken functionality in NEST that v8 has caused?
Issue Analytics
- State:
- Created 8 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Just released 1.7.2 😃 The upper limit on Json.Net has been bumped per @Mpdreamz’s commit above, so you’ll be able to upgrade in your application.
We’re going to upgrade our dependency to Json.Net 8 and release that as 1.8 shortly.
We really need this as well… Can we get a 1.7.2 out with this please.