[Beta] Support .NET Standard 1.0

This issue attempts the avenue marked Alternative in #132 : convert the PCL 259 package to make a netstandard1.0 offering for Polly, rather than the netstandard1.6 offering in #132. Rationale: A netstandard1.0 offering will have wider applicability (lower netstandard versions support wider targets).

Status and issues 02 July 2016

[1] The pre-requisite step described in Oren Novotny’s article of moving from packages.config to project.json (per an earlier article) worked, and was pushed as commit bc66df8 to this branch on my local fork.

[2] The subsequent step in the original article of moving projects from PCL259 to target instead netstandard1.0 works for both Polly.Pcl and Polly.Pcl.Specs.

[3] But, as expected, while we are awaiting xunit supporting netstandard and FluentAssertions .NET Standard support, testing is blocked in a catch22:

• (i) If we make Polly.Pcl.Specs target netstandard1.0 we cannot run the xunit tests. (per commit ea462f7) UPDATE 04 July 2016 Dennis Doomen and Oren Novotny advise against this approach: test libraries should not target .NET standard, but a specific target framework.
• (ii) If we don’t make Polly.Pcl.Specs target netstandard1.0 but Polly.Pcl does, Polly.Pcl.Specs cannot reference Polly.Pcl (obviously meaning again the tests cannot be run). (per commit 9d55469). UPDATE 04 July 2016: Something like this approach is recommended. Need to update approach to testing.

[adamhathcock]

Any chance for a beta package to get pushed to nuget?

[devlead]

@reisenberger tested your fork and beta-netstandard10 with our Cake build scripts and haven’t found any issues yet, perhaps you should have an MyGet feed for alpha releases? Allot easier to test when you can pull using nuget.