Well, it turns out that when it comes to using CloudConfigurationManager with asp.net 5, the answer is that you don't, and the boilerplate code already covered it. (Thanks to Scott Hanselman for getting back to me on twitter)
So the standard approach is something like this:
IConfiguration configuration = new Configuration()
.AddJsonFile("config.json") // adds settings from the config.json file
.AddEnvironmentVariables(); // adds settings from the Azure WebSite config
The order in which these are called means that settings from the environment variables will over-write settings from the local config. All you have to do to make use of this is make sure the Azure settings will mimic your Json settings- so if your json file looks like
{
"AppSettings": {
"ConnectionString": "blahblahblah"
}
}
You'd want to set up your setting in azure to look like
Key: AppSettings:ConnectionString
Value: blahblahblah
, and then you can go ahead and use the exact same code you'd use for the local config.
var connectionString = Configuration.Get("AppSettings:ConnectionString");
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…