Carried out a discovery phase recently to look at Azure API Management and the key features gained by layering Azure’s API Manager (APIM) as a proxy/facade layer between your backend APIs. One of the elements of APIM that rather appealed to me was the “out of the box” caching.
Was playing with a POC app recently. I pushed out a web deploy to an Azure App Service. Everything built and deployed without issue. The app fired up and nothing just the vanilla error message returned. I checked the site logs via Kudu and nothing jumped out. Tried another deploy and no dice. So where do we go from here?
<configuration> <system.web> <globalization uiCulture="en-GB" culture="en-GB" /> </system.web> </configuration> http://stackoverflow.com/questions/28430862/configuring-azure-web-and-sql-uk-culture
To enable simply click on the web app in question through the Azure dashboard. Click on the “Configure” tab and look for the “Connection Strings” section about 3 quarters down. In the “NAME” enter the name of your connection and in the “VALUE” enter the connection string. So for example in my web.config I have the following:
<connectionStrings> <add name="DB_Dev" connectionString="Server=tcp:mydbserver.database.windows.net,1433;Database=mydatabase;User Id=Bob;Password=mysecretpassword;Encrypt=True;TrustServerCertificate=False;" /> </connectionStrings>
This then appears in Azure config as follows:
I can then change my local dev config settings to whatever local dev instance I’m working on.