Skip to main content

Code Retreat Sibiu

Sambata, 28 ianuarie 2012, sunteti invitati la birourile iQuest din Sibiu la o sesiune de Code Retreat.
code-retreat-iQuest-SibiuCode Retreat este o oportunitate ca pe parcursul unei intregi zile sa scrieti cod doar de fun, fara presiunea deadline-urilor. Chiar daca nu reusesti sa termini decat cateva linii de cod, daca sunt “perfecte”, te consideram totusi “de-al nostru.” Este o ocazie in plus sa practicam ceea ce, ca dezvoltatori profesionisti de software, predicam: conceperea de cod minunat :)
Idea este simpla: se gaseste cate un partener de TDD pentru o problema de programare (tema) pentru 2×3 sesiuni de cate 45 de minute in orice limbaj doriti. Daca nu ati mai folosit TDD sau daca nu ati mai programat in echipa sa nu va fie teama: suntem prietenosi si nu va mancam de vii pentru asa ceva :)
Dupa fiecare sesiune perechile vor imparti pareri si cunostinte dobandite.
Pentru mai multe informatii:

Update: Dupa acest eveniment, cea mai interesanta sesiune mi s-a parut pair-programing cand nici unu nu avea voie sa vorbeasca. A fost o experienta extrem de interesanta. Abia astept urmatoare competie de acest gen.


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…