Try our conversational search powered by Generative AI!

Connection strings defined in Azure Portal are not picked up

Found in

Release 7.5

Created

Feb 05, 2015

Updated

Aug 19, 2015

Area

Falcon/CMS/Core

State

Closed, Fixed and Tested


Steps to reproduce

  1. Create an alloy sample project in visual studio, then deploy it to azure website.
  2. Modify the connection string in web.config to point to one database, then in Azure Management Portal, define the connection string [EpiserverDB] to point to another database.
  3. Browse the azure site from browser, and notice that EPiServer CMS still connect to the database defined in web.config instead of the database defined in Management Portal.

Expected: EPiServer CMS connect to the database defined in Management Portal
Actual: EPiServer CMS connect to the database in web.config

 
Related link: http://world.episerver.com/blogs/Henrik-Fransas/Dates/2015/1/important-information-if-you-are-having-a-episerver-site-as-a-azure-website/
 
NOTE: This bug could not be fixed without making a breaking change, so instead an app setting below is required to enable the fix for this bug.
 

  <appSettings>

    <add key="episerver:ReadOnlyConfigurationAPI" value="true" />

  </appSettings>