-
Notifications
You must be signed in to change notification settings - Fork 101
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
Outdated Newtonsoft.Json reference #614
Comments
I can't recall anymore why I pinned the json.net dependency at |
Thanks and good luck! |
It's looking good. I need to do a bit more pre-release testing, but hope to put out a new version today. |
That's great and will likely prevent many headaches (not just mine). Thanks for jumping on so quickly. |
I've published version 1.7.0-beta.2 to nuget.org. Would you mind trying that out and letting me know if you run into any issues? In one of my projects, I had to add an assembly binding redirect manually but I thought nuget was smart enough to add those automatically when a package is udpated... If it all looks good, then this will go out officially in the 1.7.0 release next week. |
Thanks. I'll give it a shot and let you know. I'm upgrading from v 1.3.4 so I may have a host of other breaking changes to wade through. |
Things seem to be working fine for me with the caveat that I don't have sophisticated needs. I am only calling CreateObject, CopyObject, GetObject, and DeleteObject. The calls all work without any alteration of code; that makes me happy. |
Thanks, that's good enough for me! I'll report back here when 1.7.0 releases. |
Nice. Thanks. Matthew Nicholson Beer On Tue, Jun 7, 2016 at 4:32 PM, Carolyn Van Slyck notifications@github.com
|
Anything preventing the project from referencing Newtonsoft.Json 8+? The current dependency is more than a year-old and that can force some creative juggling when adding openstack.net to apps/libraries requiring newer Newtonsoft.Json versions.
The text was updated successfully, but these errors were encountered: