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:
- go filesystem digest office mislay
app.config - copy
app.config.fooapp.config.foo - copy. - rename
app.config.foo - copyapp.config. - tell windows yes, i wish change file's extension.
- switch behind visible studio.
- open
settings.settingsvigilant project. - click "yes" 13 14 times vs asks me i wish new settings have altered
app.config. - 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?
Comments
Post a Comment