JsonConfig.lqs 1.1.7

.NET Framework 
dotnet add package JsonConfig.lqs --version 1.1.7
NuGet\Install-Package JsonConfig.lqs -Version 1.1.7
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="JsonConfig.lqs" Version="1.1.7" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add JsonConfig.lqs --version 1.1.7
#r "nuget: JsonConfig.lqs, 1.1.7"
#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 JsonConfig.lqs as a Cake Addin
#addin nuget:?package=JsonConfig.lqs&version=1.1.7

// Install JsonConfig.lqs as a Cake Tool
#tool nuget:?package=JsonConfig.lqs&version=1.1.7

JsonConfig.lqs is ported from JsonConfig by Timo Dörr. The original JsonConfig is great, but when I find that with it I can create only one Default config, only one User config and only one Global config in an AppDomain, I decides to create this new port. The main difference to original JsonConfig is that now you could have Default/User config per assembly, plus a global Default/User config. Additionally, I think there is no need to have a Global config given there is a User config, I removed it, and the User config is config merged from user config file and default config. At last, I also defined a plus(+) operator for ConfigObject class to simply Merge operations.

Product Compatible and additional computed target framework versions.
.NET Framework net 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
1.1.7 2,040 4/27/2015

bug fix: If a configuration value, which was in the default configuration and was not the direct child of the configuration root, was modified, it would not be saved to the user config file.