ArgumentAssertions 1.1.0

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

// Install ArgumentAssertions as a Cake Tool
#tool nuget:?package=ArgumentAssertions&version=1.1.0                

Argument Assertions provides a fluent, simple and easy to use API for checking valid argument values with strong compile time type checks.

Product Compatible and additional computed target framework versions.
.NET Framework net452 is compatible.  net46 was computed.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
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
1.1.2 1,718 4/25/2016
1.1.1 1,062 4/12/2016
1.1.0 1,059 4/10/2016
1.0.2 1,110 3/26/2016
1.0.1 1,436 3/24/2016
1.0.0 1,068 3/24/2016

Refactored ThrowIf and ThrowIfNot syntax so that the parameter details or custom exception is taken in as a parameter. Any subsequent assertion calls do not require any additional parameters. This breaks the existing implementation. Please see the project site for more details.