Skip to main content

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

By
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?
Labels:

Comments

  1. TudorMay 17, 2012 at 2:22 PM

    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

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

By
The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...
Post a Comment
Read more

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

By
Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...
Post a Comment
Read more