manage churned app config files during development

i'm building an concentration used several opposite customers. any fan satisfactory volume tradition business logic, i have skilfully refactored out an public gets hallowed during runtime. name assembly, along array customer-specific settings, stored application's settlement file.

right now, here's i have method debug concentration fan foo:

1. go filesystem digest office mislay app.config


2. copy app.config.foo app.config.foo - copy.


3. rename app.config.foo - copy app.config.


4. tell windows yes, i wish change file's extension.


5. switch behind visible studio.


6. open settings.settings vigilant project.


7. click "yes" 13 14 times vs asks me i wish new settings have altered app.config.


8. close settings.settings.

okay! i'm prepared debug!

it seems me rigamarole opening settings.settings is, ought be, unnecessary: i don't need default values settings.cs regenerated, since i don't them. nonetheless it's wholly proceed i know vs wakeful fact app.config record changed, build duplicate cost directory.

there's got an easier proceed doing this. it?