Skip to main content

Delegates from .NET 1.0 to .NET 4.0

Mai mult ca sigur ati folosit delegate. Sunt utili cand trebuie sa specificam un comportament la runtime si nu la compile time. Prin acest mecanism putem sa scapam de mostenire in locurile unde aceasta a fost folosita pentru a definii un comportament specific.
Exista mai multe tipuri de delegates definite core-ul de .NET:
  • Predicate
  • Action
  • Func
O sa incerc sa descriu pe scurt fiecare tip de delegate:
Action reprezinta o actiune care nu returneaza nici un rezultat. Header-ul la metoda ar fi de forma urmatoare
void fx(T)
Exista mai multe implementari de Action, se pot definii pana la maxim 16 parametrii. In cazul in care avem nevoie de mai mult de 16 parametri, ne putem definii noi propile actiuni, dar nu cred ca este sanatos sa avem o actiune cu 16 parametrii sau mai multi.
Predicate reprezinta o conditie care se ruleaza si care returneaza TRUE sau FALSE
bool fx(T)
Atat Action cat si Predicate apar odata cu .NET 2.0, dar ajung sa fie folosite la adevarata lor valoare abia in .NET 3.5 cand apare si Func impreuna cu expresiile lambda.
Func<T1...,TResult> specifica un delegate care accepta de la 0 la 16 parametrii si returneaza un rezultat de tipul TResult. Este bine de retinut faptul ca tipul rezultatului este definit mereu ca si ultimul parametru.
TResult fx(T1,...)
Acuma ca stim ce reprezinta fiecare din ele, ar fi interesant sa vedem cum au aparut si evoluat in timp.
In .NET 1.0 si .NET 1.1 daca aveai nevoie de un delegate era nevoie sa iti declari un delegate de forma:
delegate bool GetHalfDelegate(int number);
Urmatorul pas era declari o metoda care are aceiasi semnatura cu delegatul pe care l-ai declarat si apoi sa instantiezi o variabila de tipul respectiv.

public bool GetHalf(int number) { ... }
...
GetHalfDelegate getHalf = new GetHalfDelegate(this.GetHalf);
Pentru a putea apela acest delegate era nevoie de un apel de forma:
int result = getHalf(97);
Odata cu aparitia la .NET 2.0 apare si conceptul de metode anonime. Prin acest mecanism putem sa ne definim o logica fara a scrie o metoda. In cazul nostru nu mai este nevoie sa ne definim medoda GetHalf, ajunge doar ca in momentul in care instantiem variabila getHalf sa scriem codul care vrem sa se execute.
GetHalfDelegate getHalf = delegate(int number)
{
return number/2;
};
Lucruriile se simplifica umpic, dar cu .NET 3.5 totul ajunge mult mai simplu. Putem sa ne folosim de Func. Orice metoda definita cu acest antet o sa poata sa fie folosita. Cel care defineste metoda nu va mai avea nevoie sa aibe o referinta la tipul delegat-ului Tot ce mai este nevoie sa scriem este:
Func<int,int> getHalf = (number) => number/2;
Mi s-a parut destul de interesant modul in care sintaxa a evoluat de la 1.0 la 3.5.
In .NET 4.0 nu a mai aparut nimic special la acest nivel, dar cu ajutorul lui var putem sa rescriem codul sub forma
var getHalf = (number) => number/2;
Trebuie avut grija cat de mult folosim aceste elemente. Viteza de executie a codului poate sa scada in care face exces, iar nu in ultimul rand codul scris poate sa fie mult mai greu de inteles.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

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.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too