Username or EmailPassword
These links do not state that app.config and user.config are meant replace storage of configuration that is handled by the registry in .Net applications.
I have posted in this thread about those APIs and are nothing new to me. What you still haven't proven is that MS expects .Net developers to use these classes and not the registry! Get it?
WTH? That reply was meant for google_ninja not you!
I did, the MSDN on System.Configuration. They use a Facade pattern for the API with the ConfigurationManager class (http://msdn.microsoft.com/en-us/library/system.configuration.config...)
So where does it imply that MS expects .Net developers to use these classes and not the registry? I see no statement implying such. Please don't be vague.
The link you provided refers to app.config, which is not practical for storing user settings because of this precaution in the Notes to Implementers section:
The user or process that writes must have the following permissions:
-Write permission on the configuration file and directory at the current configuration hierarchy level.
-Read permissions on all the configuration files.