I'm just wondering why it's Settings.Default.<mysetting>
instead of just Settings.<mysetting>
?
Simply put: because Settings
is a class, and the properties are instance properties. So you need an instance, and the default way of creating an instance is through the Default
property.
The obvious followup question is why the properties aren't just static to start with... and I surmise that the answer is that it's useful to be able to create settings in ways other than with the default settings load/save approach... for example, loading them from a database, or from a different file path.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With