fresco.imagepipeline 0.1.7

dotnet add package fresco.imagepipeline --version 0.1.7                
NuGet\Install-Package fresco.imagepipeline -Version 0.1.7                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="fresco.imagepipeline" Version="0.1.7" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add fresco.imagepipeline --version 0.1.7                
#r "nuget: fresco.imagepipeline, 0.1.7"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install fresco.imagepipeline as a Cake Addin
#addin nuget:?package=fresco.imagepipeline&version=0.1.7

// Install fresco.imagepipeline as a Cake Tool
#tool nuget:?package=fresco.imagepipeline&version=0.1.7                

Image Pipeline loads images from the network, local storage, or local resources. To save data and CPU, it has three levels of cache; two in memory and another in internal storage.

Product Compatible and additional computed target framework versions.
Universal Windows Platform uap was computed.  uap10.0 is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
0.1.7 45,218 8/7/2018
0.1.6 2,975 6/5/2018
0.1.5 9,043 3/9/2018
0.1.4 2,078 3/8/2018
0.1.3 2,176 3/1/2018
0.1.2 9,696 1/16/2018
0.1.1 3,331 12/21/2017
0.1.0 1,967 11/20/2017
0.0.9 2,047 11/7/2017
0.0.8 4,969 10/10/2017
0.0.7 2,679 10/10/2017
0.0.6 2,203 10/4/2017
0.0.4 2,213 9/24/2017
0.0.3 1,884 5/15/2017
0.0.2 1,417 2/21/2017

Updates memory pool params to avoid failing on devices having memory limit as: 0-4MB, 32-~66MB.