We've seen similar issues with trying to update previous SDKs. I haven't checked, but I'd say it's the same - NuGet fails to figure out the correct dependencies. In this case, the easiest thing (!) is to uninstall the 2017.1 nuget packages and reinstall the 2017.2 ones.
Alternatively, you could change your .csproj files to the new .net core SDK style .csproj files. They still target .net framework 4.5, but have a simpler, cleaner .csproj. This is what we're doing with the Unity plugin. It does require VS2017 or Rider, though.
Matt