I have a solution that has several output projects (website, admin tool and SOAP API layer).
Each of them has common projects in the solution (service level, data level, etc.). In one of these common projects, I want to keep the configuration layer.
Right now, we have three separate appsettings configuration files for each output project -
development.AppSettings.configtesting.AppSettings.configproduction.AppSettings.config
Thus, there are nine configuration files. Only one is used in each project, since they refer to the use of the configSource attribute in the web.config node settings.
Anyhoo, it gets pain anytime we want to add / remove values ββfrom our configuration files, because that means we have to change all nine files for this. And here is what I would like to do:
In a common project, we have three configuration files, as described above. They must be copied to the output directory so that each project has a copy of them. This will be the "basic" configuration.
Then in each project I would like to have three files again, but they do not have to contain the same values ββas the base configurations. If they did, then the base configuration value would be overridden by the value in the configuration of the output project. The configuration inheritance form, I suppose.
- . .
, , ? , , , , , ?
, production.appsettings.config, , .
(//), , ?