Polly: Extra type-forwarders installed by nuget, when installing Polly for Xamarin

[lamest]

Is it possible to use Polly with Xamarin PCL projects? Xamarin.Android, Xamarin.iOS?

[reisenberger]

@lamest Polly contains a .NET Standard 1.0 target, which covers those Xamarin targets, so: Yes.

[joelhulen]

I've personally used it in Xamarin PCL projects, so absolutely!

[lamest]

I see now. My issue was that when i try to install Polly nuget package there are number of dependencies from system.* included. It's because of i target .Net 4.5.1 which is .NET Platform 1.2 (thanks @reisenberger). Isn't this so?
Is there any plans for newer .NET Platform support?

[reisenberger]

Hi @lamest
I'm not sure if this exactly answers your question, but:

• Polly targeting .NET Standard 1.0 (rather than 1.2) doesn't mean we're targeting an older build of .NET. A .Net Standard version number defines a subset of APIs that platforms implementing that .NET Standard have to implement.

• Libraries like Polly intentionally target the _lowest-numbered_ .Net Standard definition they can: they state the _smallest_ subset of .NET APIs they require, in order that they can be used by the _widest_ range of implementation platforms. So Polly being able to reference the lowest numbered .NET Standard (1.0) is a positive: it makes Polly as widely usable as possible.

• Regarding the System.* apparent dependencies installed when referencing the Polly .Net Standard 1.0 target, twsouthwick at Microsoft clarifies these are _type forwarders_. IE They aren't extra DLLs because Polly has somehow targeted a lower-numbered version of .NET Standard. It’s acknowledged that this noisiness (the multiple extra System.* references installed) is part of using the .NET Standard 1.0 approach at the moment.

Let us know if that helps!

[lamest]

Answer part with "type forwarders" is exactly what i was needed. Thanks for complete answer.

[reisenberger]

Closing due to lack of activity.