You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.
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").
The text was updated successfully, but these errors were encountered:
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.
We have first class support for connection strings defined in Azure Web Apps (formerly Azure Web Sites) which translates env vars with name like
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>
andAPPSETTING_<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 orConfiguration.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")
.The text was updated successfully, but these errors were encountered: