Just as Microsoft is constantly working to update, upgrade and add to the overall Microsoft Azure platform, they are also working to keep updating and improving the development tools to match. The current Azure .NET SDK has been around for quite some time now. While it’s stable, there may be some room for improvement to the overall Azure developer experience. Microsoft recently announced they are working on a newer set of Azure API libraries for use with the .NET Framework that are based on Fluent Interfaces. This article describes both what a “Fluent Interface” is, as well as what the new fluent Azure SDK for .NET has to offer and how it can be used. Read More
Just as all Azure Web Apps need configuration values, most applications also need to have database Connection String values configured. With Azure Web Apps the Connection Strings are stored/retrieved in a very similar fashion as Azure Web App Application Settings. Connection Strings are also Key / Value pairs of String values, but are separated out into their own section.
Connection Strings are typically used to store the connection information for one or more databases the Web App needs to connect to for storing and retrieving data. The Connection String types supported are SQL Database, SQL Server, MySQL and Custom. Most often the Connection Strings used will be for some kind of SQL RDMS, but the Custom type allows for an additional Connection String to be configured any other type of database connection necessary.
As with Application Settings, the Connection Strings are accessed as normal from .NET code and the values will come from what is set within the Azure Management Portal. In other development environments (Node.js, Java, PHP, Python) the Connection Strings are exposed to code as Environment Variables. Additionally, the Connection Strings are editable within the Azure Management Portal, but are read-only when access through code. Read More
All web applications have some kind of configurations necessary. The method of storing and accessing these settings varies on different web application platforms. In ASP.NET they are normally stored within <appSettings> element of the web.config file. The Microsoft Azure Web Apps Service allows for these application settings to be configured within the Azure Web App configurations in the cloud, and then subsequently accessed from application code as needed. With .NET applications the application settings are accessed exactly as AppSettings contained within the web.config file. In other web platforms (Java, Node.js, PHP and Python) the application settings are access via Environment Variables.
Application Settings are stored as a Key / Value pair. These are both stored as String values. Read More