Karamunting.Android.MaterialAboutLibrary 2.1.0

There is a newer version of this package available.
See the version list below for details.
dotnet add package Karamunting.Android.MaterialAboutLibrary --version 2.1.0
NuGet\Install-Package Karamunting.Android.MaterialAboutLibrary -Version 2.1.0
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="Karamunting.Android.MaterialAboutLibrary" Version="2.1.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Karamunting.Android.MaterialAboutLibrary --version 2.1.0
#r "nuget: Karamunting.Android.MaterialAboutLibrary, 2.1.0"
#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 Karamunting.Android.MaterialAboutLibrary as a Cake Addin
#addin nuget:?package=Karamunting.Android.MaterialAboutLibrary&version=2.1.0

// Install Karamunting.Android.MaterialAboutLibrary as a Cake Tool
#tool nuget:?package=Karamunting.Android.MaterialAboutLibrary&version=2.1.0

Makes it easy to create a beautiful about screen for your app. Generates an activity or fragment.
Ported to Xamarin.Android by rofiqsetiawan@gmail.com

Product Compatible and additional computed target framework versions.
MonoAndroid monoandroid71 is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

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
2.2.3 1,866 10/1/2017
2.1.0 997 6/28/2017

In this release:

* Fixed issues with colour primary in fragments #60 (MaterialAboutFragment's getTheme function now requires a theme)
* @k0shk0sh added custom card colours in PR #61
* This addition also applies to #57

Thanks to @k0shk0sh for contributing!