Skip to main content

Configuration settings from Windows Azure Service Configuration Schema (cscfg) is always null

Last day, one of my colleges had to move some configuration items from application configuration file to cscfg files (Windows Azure Service Configuration Schema).
He tried for some hours to move the configuration to cscfg files but without success. Even if the configuration was done 1 to 1 to the msdn example and the project was built and deployed with success, the configuration could not be accessed.
In the next part of the post I will describes the steps that were done by him:
      1. Identify the configuration that need to be moved in the configuration file:
<add key="BingKey" value="XXXXXXXXXXXXXXXXX" />
      2. Create the key definition in the csdef (Windows Azure Service Definition Schema) file:
<ServiceDefinition ..
    <WebRole ...
        <ConfigurationSettings>
            <Setting name="BingKey" />
        </ConfigurationSettings>
    </WebRole>
<ServiceDefinition>
      3. Add the value of the given configuration key to the cscfg file (cloud and also local configuration):
<ServiceConfiguration ...
    <Role ...
        <ConfigurationSettings>
            <Setting name="BingKey" value="XXXXXXXXXXXXXXXX" />
        </ConfigurationSettings>
    </Role>
</ServiceConfiguration>
      4. Access the configuration key:
string bingKey = ConfigurationManager.AppSettings[“BingKey”];
Every time when the key is retrieved, the return value is null. If we check the settings, we will notify that we cannot find the “BingKey” through the list of available setting. 
Did you spot the problem?
The configuration was made perfectly; the problem was with at step 4. When we want to access configurations from cscfg file we need to use the RoleEnvironmnet and not the ConfigurationManager. The configurations from cscgf files will not be available through AppSetings collection.
The code should be changed to something like this:
string bingKey = RoleEnvironment.GetConfigurationSettingValue("BingKey");
After this fix everything works perfectly. For more informations about RoleEnvironment please check the following link.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...