Simple, cross-platform settings framework based on the idea of many distinct settings classes are better than one huge one. Persistence is configurable, as is the location.

Every application requires user-, application-, and other defined settings. The maintenance of these settings can be horrendous over time if not property architectured and maintained.

SimpleSamSettings aims to ease the burden of creating, managing, saving, and restoring settings for any application in .NET Standard.

Available on nuget here

• See the SimpleSamSettings.Demo WPF application

public class MySettings : OverwriteSettingsProfile<MySettings> 
{
   public string SomeProp
   {
      get => Get<string>();
      set => Set(value);
   }
}

Globals.SettingsFileBasePath = Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData), "MyAppName");

That's it! Your settings will be persisted to %appdata%/MyAppName/MySettings.settings in JSON format. Prefer binary? No problem! Put the [Serializable] tag on it and it will auto-serialize as binary.

By default, each change updates the file on disk. To turn off this behavior, simply set AutoSave to false, like this:

var settings = new MySettings() { AutoSave = false };

...then at any time, you can save it (say, on application exit):

settings.SaveInstance() OR MySettings.Save(); // OverwriteSettingsProfile<> ensures a singleton instance, so it is a static helper method

Say you have a dialog open for the user to change settings. The settings changes are live, ideally, but if the user clicks 'Cancel' everything they've done during the lifetime of that dialog should be undoe. Easy peasy!

Simply set the 'MakeUndoable' flag in the base to C#true.

settings.MakeUndoable = true;

... do your stuff in the dialog ...

To cancel or undo everything:

settings.RevertChanges();

Then set MakeUndoable back to false so it doesn't save off changes:

settings.MakeUndoable = false;

Encapsulate your settings into small classes - many, properly encapsulated classes is preferred over one or a few very large ones! This makes it easier to maintain, easier to use and reuse, and speeds up disk i/o.

If a collection or object inside the settings class changes, the file will not be autosaved. It is recommended that the settings class listen for changes on those objects and auto-saves them, as appropriate, but this is in no way enforced and left entirely up to the consumer (you). Happy settings coding!

Brent Bulla (@outbred)

If you found this project helpful or you learned something from the source code and want to thank me, consider buying me a cup of - PayPal

Even though this repo is new, this architecture behind this framework has been in production and used by me for several years now on several different projects. I've re-written it for open source consumption, but it is not something that I've just now come up with - I've refined it and simplified it over the years into something that (now) I think is worthy of sharing with the world.