Skip to main content

Tuplu in C#, am luat taurul de coarne

Ce este un tuplu? Este o metoda de a grupa elemente de tipuri diferite. Apare mai ales in cadrul limbajelor funcționale sau dinamice precum Python.
De exemplu daca trebuie sa stocam coordonatele unui punct in spatiu putem sa avem (12,"C",23.3m). Fiecare axa poate sa aiba o unitate de masura diferita.
In C# 4.0 avem o clasa statica ajutatoare denumita Tuple, care ne ofera posibilitatea sa cream un tuplu cu pana la 8 tipuri generice( Tuple.Create(T1,..,T8) ).
Pentru exemplul de mai sus ar trebui sa avem urmatorul obiect:
var point=Tuple.Create<int,string,decimal)(12,"C",23.3m)

Daca vrem sa cream un tuplu care sa contina 23.3m si 40m pe axa 0z atunci putem sa cream un nou tuplu pe pozitia a 3-a.
var point=Tuple.Create(12,"C",new Tuple<decimal,decimal>(23.3m,40m)

Prin aceasta modalitate putem sa stocam coordonatele unor forme geometrice.
In cazul in care ajungem sa avem nevoie de un Tuplu cu mai mult de opt elemente generice atunci putem pe ultima pozitie definim un nou tuplu. Pentru a ne face munca mai usoara, ne putem defini niste clase ajutatoare care sa ne ofere tupluri de 9,10 sau n dimensiuni. Din pacate nu putem sa extindem metoda Create deoarece nu putem scrie extension method pentru metodele statice.
Atentie, nu putem itera un tuplu. Putem sa accesam fiecare element a unui tuplu prin proprietatile: Item1, Item2, ... , Item8.
Un tuplu se poate folosi ca un tip de data ajutator cand trebuie sa stocam temporar anumite date care nu au o legatura directa intre ele. Poate sa fie folosit cu succes cand vrem sa inlocuim clasele temporare folosite pentru a obtine de la DAL pentru a le trasmite spre UX sau orice rezultat care returneaza mai multe valori.

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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

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