LitJSON

A .Net library to handle conversions from and to JSON (JavaScript Object Notation) strings.

It's quick and lean, without external dependencies. Just a few classes so easily embeddable in your own code or a very small assembly to ship with your code. The code is highly portable, which in general makes it easy to adapt for new platforms.

Continuous integration

Build server	Platform	Build status
AppVeyor	Windows
Bitrise	MacOS
Bitrise	Linux
Azure Pipelines	Linux / MacOS / Windows
GitHub Actions	Linux / MacOS / Windows

Compiling

Code can be compiled using .NET CLI or by launching the bootstrappers in the root of the repository.

Windows

./build.ps1

Linux / OS X

./build.sh

Prerequisites

The bootstrappers will (locally in repo)

• Fetch and install .NET Core CLI / SDK version needed to compile LitJSON.
• Fetch and install Cake runner
• Execute build script with supplied target (--target=[Target]) or by default
  1. Clean previous artifacts
  2. Restore build dependencies from NuGet
  3. Build
  4. Run unit tests
  5. Create NuGet package

Testing

This library comes with a set of unit tests using the NUnit framework.

Using LitJSON from an application

Package manager

Install-Package LitJson -Version 0.19.0

.NET CLI

dotnet add package LitJson --version 0.19.0

Paket CLI

paket add LitJson --version 0.19.0

Alternatively, just copy the whole tree of files under src/LitJSON to your own project's source tree and integrate it with your development environment.

Requirements

LitJSON currently targets and supports

• .NET 8
• .NET 6
• .NET Standard 2.1
• .NET Standard 2.0
• .NET Standard 1.5
• .NET Framework 4.8
• .NET Framework 4.5
• .NET Framework 4.0
• .NET Framework 3.5 (including SQLCLR, for which WCOMAB/SqlServerSlackAPI is an example of)
• .NET Framework 2.0
• Mono 4.4.2 and above

Prereleases

Each merge to develop is published to our NuGet feed on MyGet and also GitHub Packages.

Contributing

So you’re thinking about contributing to LitJSON? Great! It’s really appreciated.

• Create an issue
• Fork the repository.
• Create a feature branch from develop to work in.
• Make your feature addition or bug fix.
• Don't forget the unit tests.
• Send a pull request.

License

Unlicense (public domain).