This is sort of an update of my AoOptions project, moving it from XML to Json, and removing the WinForms dependency. It was also important that I support a DPAPI encryption on properties, since the intended use case for this is to store sensitive things like database connection strings and other credentials. More info about DPAPI is here.
Nuget package: JsonSettings.Library
Note, as of 1/21/19, version 1.0.8 replaces the package AoJsonSettings in order to target .NET Standard 2.0.
-
Create a class for your app settings based on SettingsBase abstract class and implement the Filename property.
-
If you need to encrypt a string property, add the [JsonProtect] attribute to the property. Props to this SO answer from Brian Rogers on implementing the custom attribute that does this.
-
Instantiate your settings class with
JsonSettingsBase.Load<T>
whereT
is your settings type. -
Use the
Save
method to persist any modified settings to disk.
var settings = SettingsBase.Load<MySettings>();
// when app closing or on some other event:
settings.Save();
Encrypted property example:
public class AppSettings : SettingsBase
{
public override string Filename => BuildPath(Environment.SpecialFolder.LocalApplicationData, "AppSettings.json");
public string Greeting { get; set; } = "hello";
[JsonProtect(DataProtectionScope.CurrentUser)]
public string SensitiveValue { get; set; }
}
If you don't need the built-in settings file handling logic, you can use the JsonFile static class with its Load
, Save
(and LoadAsync
, SaveAsync
) methods to make it easy to save any json data to a file. The [JsonProtect] attribute still works in this usage.