SettingsDb is a .NET Standard library that allows to manage persistence of application settings in a simple and fast way. Settings values are serialized as JSON objects and stored in a database. This offers a great level of flexibility in terms of what type of data can be stored.
Any type of database can be used, as long as there is an specialization of DbConnection for it.
Using NuGet package manager console:
Install-Package SettingsDb
Using .NET CLI:
dotnet add package SettingsDb
Just create an instance of the SettingsDb class specifying the type of connection, the connection string and (optionally) the database table to use. If no table name is specified, "Settings" will be used.
// Use a SQL Server database to store the settings.
var settings = new DbSettings<SqlConnection>("Database=myDataBase");// Use a SQL Server database to store the settings in the "AppSettings" table.
var settings = new DbSettings<SqlConnection>("Database=myDataBase", "AppSettings");When using a SQLite database, Settings class can be used instead. Settings acts as a shortcut for DbSettings<SqliteConnection> and provides backwards compatibility with previous versions of the library.
// Use SQLite to store the settings.
var settings = new Settings();
// This is equivalent to use:
var settings = new DbSettings<SqliteConnection>($"Data Source={Assembly.GetEntryAssembly().GetName().Name}.Settings.db");// Use SQLite to store the settings in the "AppSettings" table.
var settings = new Settings("AppSettings");
// This is equivalent to use:
var settings = new DbSettings<SqliteConnection>($"Data Source={Assembly.GetEntryAssembly().GetName().Name}.Settings.db", "AppSettings");// Use SQLite to store the settings in the "AppSettings" table, using "Settings.db" as the database file name.
var settings = new Settings("Settings", "AppSettings");
// This is equivalent to use:
var settings = new DbSettings<SqliteConnection>("Data Source=Settings.db", "AppSettings");When a new instance of the Settings class is created, it checks for existence of the database file and creates it if necessary. By default, the assembly name of the application will be used as the database name, but you can specify any other name in the constructor.
To store a value, just call the Store method (or its async version StoreAsync) passing the name to be used for the setting and its value:
public void Store<T>(string settingName, T value);
public async Task StoreAsync<T>(string settingName, T value);var settings = new Settings();
settings.Store("UserName", "John Doe");
settings.Store("ID", 12345);
await settings.StoreAsync("ShowToolbar", true);If a setting with that name already exists, its value is replaced.
Remember that specified values are serialized to JSON strings prior to be stored into the database, so you can even pass in simple objects:
class WindowPosition
{
public int X { get; set; }
public int Y { get; set; }
}
var settings = new Settings();
settings.Store("WindowPosition", new WindowPosition { X = 250; Y = 100});To read a value from the database, you use any of the Read or ReadAsync generic methods, passing the name of the setting, the expected type to be returned
and, optionally, a default value to be used if the specified setting is not found in the database.
public T Read<T>(string settingName, T defaultValue = default);
public async Task<T> ReadAsync<T>(string settingName, T defaultValue = default);var settings = new Settings();
var showToolbar = settings.Read<bool>("ShowToolbar", true);
var windowPosition = await settings.ReadAsync<WindowPosition>("WindowPosition");If no default value is specified and the setting name is not found, SettingsDb will return the default value for the requested data type.
public void Clear(string settingName);
public Task ClearAsync(string settingName);public void ClearAll();
public Task ClearAllAsync();public long Count();
public long CountAsync();