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 ...
            <Setting name="BingKey" />
      3. Add the value of the given configuration key to the cscfg file (cloud and also local configuration):
<ServiceConfiguration ...
    <Role ...
            <Setting name="BingKey" value="XXXXXXXXXXXXXXXX" />
      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.


Popular posts from this blog

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 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.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.