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

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…