We're using a .settings file to store our application settings, and use default values in there so that we don't need to configure every single setting. This has generally been fine.
However, during development we'll frequently change values in app.config, which means that when we open the .settings file, we always get the prompt "Value of setting 'x' was changed in the app.config file. Do you want to update the value in the .settings file?"
In our case, the correct thing to do is always click No, otherwise development settings can slip through to test and production environments with relative ease. But, since we're human, that's not always what happens. What's worse, the default button is "Yes".
Can we remove the human element somewhat and make Visual Studio not ask us this? Or should we give up on relying on default settings and define an explicit entry in app.config for every single setting in every single environment?