For most applications the *out of box* functionality of the System.Configuration classes work well. However, there are situations when you need a better way to handle multiple sets of configuration data. For example, you may need a set of configuration data per environment (e.g. development, systems integration test, user acceptance test, production, contingency, training, demo, load test, etc.). DCM allows you to segment your app.config file into configuration maps. Each configuration map represents an environment and includes application key/value pairs. The application key/value pairs for a configuration map is dynamically loaded based on configuration map attributes at runtime.
Get Started
$ dotnet add package DCMReadme
No README available.