Skip to main content

Azure - How to add custom settings to a Windows Azure project

In acest post o sa vedem cum se pot adauga configurari custom in cadrul proiectului Windows Azure, iar apoi sa le putem accesa din cod.
O parte din configurariile unei aplicatii se tin de obicei in fisierul de configurare (app.config sau web.config - de la caz la caz). Insa, cand lucram la un proiect care o sa ajunga in Windows Azure putem sa facem aceste configuratii si in alta locatie.
De exemplu putem ca aceste configuratii sa le tinem in proiectul de deploy pentru cloud. In felul acesta, putem sa avem mai multe configuratii pentru mai multe environment si/sau chiar sa avem configuratii diferite pentru local si cloud fara sa ne definim un mecanism special pentru acest caz.
Primul pas care trebuie facut este sa deschim fisierul ServiceDefinition.csdef din proiectul de deploy pentru Windows Azure. In cadrul acestuia sub nodul WebRole sau WorkerRole (depinde unde aveti nevoie) este nevoie sa adaugam un nod denumit ConfigurationSettings. In acesta este nevoie sa ne definim lista de configurari custom de care noi avem nevoie.
<WebRole name="Foo.Web" vmsize="Small">
<ConfigurationSettings>
<Setting name="MyCustomFlag">
</onfigurationSettings>
</WebRole>
Odata ce am definit aceasta lista, o sa putem observa ca daca deschidem rolul pentru care am definit aceasta configuratie, putem sa gasim in tab-ul de Settings si configuratia noastra. Valoarea acestuia se poate seta si manual direct in fisierul ServiceConfiguration.Local.cscfg pentru local si ServiceConfiguration.Cloud.cscfg pentru versiunea care ajunge in cloud.
In interiorul acestui fisier in urmatoarea locatie "ServiceConfiguration/Role/ConfigurationSettings" este nevoie sa adaugam un nod care sa aibe urmatoarea forma:
<Settings name="MyCustomFlag" value="256" />
Deoarece aceasta valoare poate sa fie setata diferit pentru local sau pentru cloud, mi se pare foarte utila.
Singurul lucru care ne-a ramas este sa accesam setarea noastra din cod. Acesta este cel mai usor pas, tot ce este nevoie este sa apelam metoda GetConfigurationSettingValue din cadru RoleEnvironment.
string  myCustomFlagValue = RoleEnvironment.GetConfigurationSettingValue("MyCustomFlag");
Ce parere aveti? Ati folosi aceasta varianta?

Comments

  1. Nu doar ca as folosi-o, ci e cam singura solutie recomandata pe Azure, unde avem in mod normal mai multe role instances ruland in acelasi timp - web.config fiind separate pentru fiecare instanta, setarile e logic sa fie intr-o locatie centralizata (cscfg), nu in web.config.

    ReplyDelete

Post a Comment

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...