We use the .settings file to store our application settings and use the default values ββthere, so we do not need to configure each individual setting. This was usually good.
However, during development, we often change values ββin app.config, which means that when we open the .settings file, we always get a prompt . The value of the parameter "x" has been changed in the application. config file. Do you want to update the value in the .settings file? "

In our case, the right thing is to always select βNoβ , otherwise the development parameters can easily slip into test and production environments. But since we are human beings, this is not always what happens. Even worse, the default button is Yes.
Is it possible to remove the human element a little and make Visual Studio not ask about it? Or should we abandon the use of default settings and define an explicit entry in app.config for each individual parameter in each separate environment?
Gavin
source share