Skip to content
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.

Support for Azure App Settings #207

Closed
sayedihashimi opened this issue May 19, 2015 · 1 comment
Closed

Support for Azure App Settings #207

sayedihashimi opened this issue May 19, 2015 · 1 comment
Milestone

Comments

@sayedihashimi
Copy link

We have first class support for connection strings defined in Azure Web Apps (formerly Azure Web Sites) which translates env vars with name like

SQLAZURECONNSTR_DefaultConnection
SQLCONNSTR_sqlservercs
CUSTOMCONNSTR_customcs
MYSQLCONNSTR_mysqlhere

To be compatible with the Configuration object. The code which does this is here.

We should have the same for app settings. In Azure Web Apps when you create an app setting two env vars are created, in the form <env-var-name> = <value> and APPSETTING_<env-var-name>=<value>. When a user defines a new env var in the portal they should be able to use the AppSettings class in the project that VS creates or Configuration.Get("AppSettings:SettingName") to get the value.

Today users can get to the value but they cannot use the AppSettings class, but instead something like Configuration.Get("SettingName").

@glennc glennc added this to the Backlog milestone Jul 17, 2015
@divega
Copy link

divega commented Feb 17, 2016

In #376 we are proposing to move to a model in which we don't prepend prefixes to names of keys for connection strings for Azure Web Apps. If we do that, we shouldn't do what this item describes either.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants