Skip to main content

Cat de puternic trebuie sa fie un framework sau o tehnologie ca sa schimbe ceva?

Problema se pune in felul următor: ce trebuie sa contina un framework sau o tehnologie ca sa schimbe ceva si sa fie folosit la scara mare?
Pornim de la cazuri reale:
  • MEF nu a avut un impact foarte mare - este greu sa convingi lumea sa folosesca recomandările tale, mai ales ca in fiecare firma exista deja un framework ajutator;
  • EF nu a avut nici un impact major, NHibernate inca exista( NHibernate este deja un produs matur care a trecut de problema: ce a fost prima data. EF inca nu este un produs matur in totalitate, unele funcționalități inca lipsesc);
  • ASP.NET MVC a batut tot, proiecte de gen MonoRail au fost rase;
  • Prism - o aplicatie care a ajuns la o masa critica si incepe sa fie integrata de catre M$;

Exista proiecte care au nevoie de o masa critica pentru a reuși. De exemplu Oslo Project( cu limbaj M). Un proiect indraznet, in care M$ a investit foarte mult, dar din pacate a fost oprit. Acesta concureaza direct cu EF si nu a ajuns sa fie folosit atat de mult incat sa supraviețuiască.
Un lucru important este ca in ultimul timp M$ face parte din puținele firme care investesc bani in cercetare si vor sa aduca ceva nou pe piata( totul e marketing, dar avem si noi de castigat).

De ce am scris acest articol? Am fost implicat anul trecut într-un proiect care urma sa folosească limbajul M la baza unui DSL si am avut o mare dezamăgire sa aflu ca proiectul Oslo de la M$ a fost întrerupt. Daca s-ar fi ajuns sa se faca o implementare completa a limbajului M, s-ar fi ajuns intr-un moment critic, deoarece acest proiect are in momentul de fata cateva buguri destul de grele.

Comments

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 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 …

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…

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.
publ…