Skip to main content

Luni 09.04.2012 - Emisiune live despre Windows Azure

Luni, 09.04.2012, am fost invitat sa particip la un TeckTalk de catre comunitatea ITSpark. In cadrul acestei emisiune o sa discutam despre Windows Azure. Mai jos gasiti subiectele pe care o sa le abordam in cadrul emisiunii:
  • Windows Azure - overview
  • Componentele Windows Azure
  • Azure Development do-s and don't-s
O sa incercam sa discutam si despre bunele practici in dezvoltarea aplicatiilor pe aceasta platforma.
Emisiunea se va trasmite LIVE de la ora 18:00 la urmatoarea adresa In cadrul emisiunii puteti sa ne puneti orice intrebare legata de acest subiect. In cazul in care nu puteti sa ne urmariti live, puteti oricand sa urmariti emisiunea la urmatorea adresa
Sa nu uitati ca vizionarea acestei emisiuni este GRATIS atat in versiune live cat si offline. Ne vedem luni de la ora 18:00.

UPDATE: La urmatoarea adresa puteti sa urmariti emisiune offline


  1. Mi-am pus un reminder si sper sa va vad live. Am vazut-o si pe Steliana in episodul 9.

  2. Te asteptam luni intr-un nou episod.


Post a Comment

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…