Skip to main content

Opt greseli de design care ne pot afecta aplicatia

Am inceput sa studiez design patterns si am inceput cu o carte de a celor de la Gof (Gang of Four). In aceasta carte am gasit opt greseli de design care ne pot afecta aplicatia:
  1. Crearea unui obiect folosind numele unei clase explicit. In acest fel ajungem sa fim legati direct de o anumita implementare. Pentru a evita acest lucru putem sa folosim o interfata, iar instanta sa o cream in mod indirect, de exemplu printr-un factory.
  2. Dependinte directe fata de sistemul hardware sau software. In cazul in care aplicatia noastra depinde in mod direct de anumite resurse ale sistemului portabilitatea scade in mod direct. Pentru aceaste cazuri putem sa incercam sa folosim un patern precum bridge, pentru a scadea dependintele.
  3. Dependintele fata de o anumita operatie. Cand specificam o anumita operatie, limitam ca lucrurile sa se intample intr-o singura varianta si numai una. Modific─ârile care o sa apara in viitor o sa necesite mai mult timp, deoarece totul este hard-codat.
  4. Dependinta fata de algoritm. De obicei pe parcursul dezvolt─ârii unei aplicatii un algoritm se schimba, din aceasta cauza algoritmii ar trebuii sa fie izolati si schimbati cu usurinta.
  5. Extinderea functionalitatilor prin subclase. In momentul in care trebuie sa adaugam o noua functionalitate, putem foarte simplu sa mostenim din clasa parinte si sa adaugam o noua functionalitate. Dar acest lucru implica sa cunoastem foarte bine clasa de baza, iar in timp poate sa duca la existenta unui numar foarte mari de clase. Acest lucru se poate rezolva prin delegation si composition. Aceste doua mecanisme ne permite sa adaugam functionalitati fara sa avem o inlantuire de subclase.
  6. Clase strans legate intre ele. In momentul in care ajungem sa avem o colectie de clase care sunt strans legate intre ele sistemul devine monolit. Orice modificare ajunge sa fie extrem de greu de facut si necesita cunoasterea foarte buna a sistemului.
  7. Imposibilitatea de a modifica anumite clase. Uneori avem nevoie sa modificam clase la care nu avem acces la codul sursa sau necesita modificarea unui numar mare de subclase. Pentru a evita acest lucru putem sa folosim Adapter sau Visitator pattern.
  8. Dependinte directa fata de un obiect sau o implementare. Este reprezentat in cazul in care o clasa conoaste modul in care o alta clasa functioneaza si este implementat. Modificarea aceste clase poate sa cauzeze modificari in cascada la toate clasele care folosesc clasa respectiva.


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…