Orthogonal.Jasper
1.0.3
This was an experimental package for private use that was published before I discovered that packages can never be deleted. Now this useless package is stuck here forever.
dotnet add package Orthogonal.Jasper --version 1.0.3
NuGet\Install-Package Orthogonal.Jasper -Version 1.0.3
<PackageReference Include="Orthogonal.Jasper" Version="1.0.3" />
<PackageVersion Include="Orthogonal.Jasper" Version="1.0.3" />
<PackageReference Include="Orthogonal.Jasper" />
paket add Orthogonal.Jasper --version 1.0.3
#r "nuget: Orthogonal.Jasper, 1.0.3"
#:package Orthogonal.Jasper@1.0.3
#addin nuget:?package=Orthogonal.Jasper&version=1.0.3
#tool nuget:?package=Orthogonal.Jasper&version=1.0.3
The Jasper packages are now practically obsolete and have been hidden. It was originally an attempt to create a general purpose schema-less object database library which used Azure Table Storage as the backing storage. The recent rise in popularity of cloud-based document databases is the main reason Jasper is obsolete. You can for example use Microsoft's high-capacity, high-speed Cosmos DB to treat arbitrary objects like documents and serialize them to-and-from the database where they are stored as fully indexed JSON documents. The original Jasper Wiki page remains published for historical interest.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET Framework | net45 is compatible. net451 was computed. net452 was computed. 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. |
-
- WindowsAzure.Storage (>= 7.2.1)
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 |
|---|
Fixed Issue #1 so that DateTime and DateTimeOffset property values are round-tripped exactly with the Ticks and Kind unchanged. See the Bitbucket issue resolution notes for an explanation of this slightly controversial behaviour. Fixed Issue #2 so that DeleteAll does not fail if the table is empty.