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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP