Target netstandard2.0 #17
Description
As per the discussion in David Fowler's tweet here, the current recommendation seems to be that all packages that can target netstandard2.0 should do so (even if it's just alongside their existing netstandard1.x target). One of the main benefits of targeting 2.0 is that consumers of the library get a much simplified dependency graph when referencing the package. David does a good job of explaining further.
FluentCache is currently targeting netstandard1.1. I think it would be worthwhile targeting both netstandard1.1 and netstandard2.0 in a future build, for the reasons outlined above.