This came up during usage, but saving config to the registry is problematic when trying to run multiple instances of the manager, or backing up the managers configuration for if the config gets corrupted.
I propose, (and an chomping at the bit to write) that the config gets saved in a json or xml document that can be modified or saved by a user.
C# has services for saving config with xml using the .config file, however there are some complications where it discriminates between setup and user state, and it saves user state to appdata instead of a more obvious location.
Json would be good too, can save that wherever, preferably not in a fixed location, possibly right next to the exe. Problem is the standard .NET json library, Newtonsoft.NET is an additional dll, it's easy to add a reference and get it copied to the output via nuget, but that would mean your download has an additonal dll file (fody or ILMerge can stitch them together though).
Personally I like json, but the additonal dll may be a dealbreaker for you, what do you think @ownprox ?
This came up during usage, but saving config to the registry is problematic when trying to run multiple instances of the manager, or backing up the managers configuration for if the config gets corrupted.
I propose, (and an chomping at the bit to write) that the config gets saved in a json or xml document that can be modified or saved by a user.
C# has services for saving config with xml using the .config file, however there are some complications where it discriminates between setup and user state, and it saves user state to appdata instead of a more obvious location.
Json would be good too, can save that wherever, preferably not in a fixed location, possibly right next to the exe. Problem is the standard .NET json library, Newtonsoft.NET is an additional dll, it's easy to add a reference and get it copied to the output via nuget, but that would mean your download has an additonal dll file (fody or ILMerge can stitch them together though).
Personally I like json, but the additonal dll may be a dealbreaker for you, what do you think @ownprox ?