.NET applications developed using Visual Studio have an easy way to store and recover user settings. You can add the default value of a setting in a special class and have read/write access to it at run time through Properties.Settings.Default.SettingName.Some applications have use for values to be remembered between sessions, which will have to be stored somewhere else than in memory. One possibility would be to create a file of a specific format (XML, JSON, ini, or something else) in the user's data directory and use it for such values.The settings described above are essentially such a file, but the values that need to be remembered might not technically be settings. One example is the timestamp of the last time a certain function was performed.One might argue against storing such a value in Properties.Settings as it is not a setting (i.e. user preference) and therefore the namespace's name would cause confusion.Is there, however, a practical reason not to use Properties.Settings to store such a value?
Is there a practical reason not to use a .NET setting to store data that is not a setting?
.net;persistence;settings