Config.json property replacement in ASP.NET Core

Question

I have the following on an ASP.NET Core Startup:

builder
  .AddJsonFile("config.json", false)
  .AddJsonFile($"config.{hostingEnvironment.EnvironmentName}.json", true);

This way I can use the config files:

config.json
config.development.json
config.production.json
config.staging.json

If I have a property that is different in production but the same in development and staging should I place that property on config.json and other one in production to replace the valie in config.json?

Or do I need to add the property in config.development.json, config.production.json and config.staging.json and remove it from config.json?

I mean, is there property replacement in ASP.NET Core configs like there was in Web.config of ASP.NET 4?

if you have more than one configuration source and the property exists in more than one source, then the last source wins, so the order of adding configuration sources is important — Joe Audette
– Joe Audette, Commented Apr 29, 2016 at 18:42
In my case I always add config.json first and one of the other after, so that means that I have a property in config.json and another value only in config.production.json to replace the base one. This was what I wasn't sure ... Thanks — Miguel Moura
– Miguel Moura, Commented Apr 29, 2016 at 18:46

Mike · Accepted Answer · 2016-04-29 18:50:22Z

1

Here is the source code that shows that config files are traversed in reverse order link

foreach (var provider in _providers.Reverse())

Any key in config.{hostingEnvironment.EnvironmentName}.json would override same key in config.json

answered Apr 29, 2016 at 18:50

Mike

4,0713 gold badges22 silver badges32 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Config.json property replacement in ASP.NET Core

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related