PushBulletSharp 2.3.2

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

// Install PushBulletSharp as a Cake Tool
#tool nuget:?package=PushBulletSharp&version=2.3.2

A simple C# wrapper to PushBullet's HTTP API.

There are no supported framework assets in this 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
3.1.0 10,277 1/24/2018
3.0.1 3,892 11/8/2016
3.0.0 1,224 11/8/2016
2.3.3 13,174 1/6/2016
2.3.2 1,680 10/26/2015
2.3.1 1,634 10/16/2015
2.3.0 1,297 10/15/2015
2.2.1 1,569 10/8/2015
2.2.0 2,036 10/8/2015
2.1.1 1,692 8/31/2015
2.1.0 1,500 8/23/2015
2.0.0 1,644 5/25/2015
1.5.0 1,556 3/26/2015
1.4.1 1,362 3/21/2015
1.4.0 1,865 10/19/2014
1.3.0 1,258 10/5/2014
1.2.1 1,272 9/15/2014
1.2.0 1,498 9/14/2014
1.1.0 1,505 9/14/2014
1.0.0 1,458 9/14/2014

Another hotfix by github user @DriesPeeters:

I fixed a bug regarding getting pushes using the Modified attribute. In the old code, the modified unix time string was not in the correct timezone. The modified attribute for the request needs to be in UTC time. In the old code, this is not always the case.

I also added a test that will normally fail with the old code, and that will succeed in the fixed code.

The test pushes a note, waits for some time, then pushes a new note. After that, we get all pushes that are modified since we pushed the first note.

--------------------

As always, thank you very much to all users who help out with this project!