Skip to main content

OutputCache in Windows Azure folosind AppFabric.Cache

In post-ul anterior am vorbit despre cum putem sa ne definim propriul nostru mecanism de cache-ing. Dar daca ne aflam in cloud.
Iata urmatorul scenariu: avem o aplicatie MVC 2 pe Windows Azure si vrem sa putem folosii un mecanism de cache-ing. In cazul in care avem mai multe web roluri dorim sa facem un sistem de cache-ing oarecum centralizat. Nu dorim sa încărcam de doua ori anumite date daca acestea sunt deja incarcate.
O varianta pentru a rezolva aceasta problema este sa ne definim propriul mecanism pentru cache-ing. Nu ar fi foarte complicat, dar ne-ar costa ceva timp. Cea mai simpla varianta este sa folosim mecanismul intern de pe Windows Azure. AppFabric ne ofera si posibilitatea sa facem cache-ing la date. Acest provider de cache-ing se numeste DistributedCache, iar pentru al putea folosi este nevoie sa accesam sectiunea de AppFabric din contul de Windows Azure si sa adaugăm un serviciu.
In web.config-ul aplicatiei trebuie sa adauga o noua sectiune prin care sa putem definii providerul din cloud, iar apoi sa scriem definiția propriu-zisa:
<section name="distributedCache"
allowLocation="true" allowDefinition="Everywhere"/>
<distributedCache deployment="Simple">
<host name="" cachePort="80" />
<securityProperties mode="Message">
<messageSecurity authorizationInfo="43423423DFJF2rf32f23f23f233gt23f3f3">
Tot ce mai este nevoie este sa adaugam in sectiunea de cache-ing definitia noastra de provider:
<outputCache defaultProvider="DistributedCacheProvider" >
<add name="DistributedCacheProvider"
cacheName="cacheOne" />
Din acest moment aplicatia noastra o sa poata folosi cache-ing pe care Windows Azure il pune la dispozitie prin intermediul AppFabric. Pentru acest lucru aveti nevoie nu doar de un cont de Windows Azure ci si de un service namespace pe AppFabric, care nu este gratis.


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 …

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.

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…