Skip to main content

ReadOnlyCollection

Va mai aduceti aminte ca in C++ puteam sa declaram o variabila sa fie constanta, fara a ne face probleme ca un utilizator ii poate schimba valoarea. In C# putem sa facem un lucru asemanator folosindu-ne de readonly.
public class Car
{
internal readonly int _id;

public Car(int id)
{
_id = id;
}
}
Doar in contructor se va putea initializa field-ul _id. Valoarea acestui camp nu se va putea modifica in nici o locatie din cod. Dar daca in loc de int am aveam o lista, ar aparea probleme. Chiar daca nu se va putea instanta din nou acest camp, continutul acestuia se va putea modifica.
public class Car
{
internal readonly List<Component> _components;

public Car(List<Component> components)
{
_components = components;
}
}

public class Logan : Car
{
// ...

public void SomeMethod()
{
_components.Add(..);
_components.Remove(..);
}
}
Oricine ar putea sa adauge sau sa stearga elemente din lista. Am avea nevoie de o lista care sa permita doar operatii de read. Pentru acest lucru .NET ne vine in ajutor si ne ofera clasa generica ReadOnlyCollection. Aceasta colectie nu contine metode prin care putem sa adaugam elemente sau sa stergem elemente din lista. Totodata indexer-ul ne permite sa facem doar get si atat.
Orice lista contine metoda AsReadOnly(), care ne returneaza o lista de tip ReadOnlyCollection.
List<int> items = new List<int>(){ 1, 2 ,3};
items.Add(4);
items.Remove(1);
items[1] = 10;
ReadOnlyCollection<int> itemsReadOnly = items.AsReadOnly();
itemsReadOnly.Add(4); //Eroare la compilare, metoda nu exista;
itemsReadOnly.Remove(1); //Eroare la compilare, metoda nu exista;
itemsReadOnly[1] = 10; //Doar get se poate face;
Chiar daca incercam sa facem apoi o conversie la List, nu o sa putem, .NET ne returneaza o eroare de genul: collection is read-only.
Exemplul dat cu clasa de tip Car, poate sa rescris in forma urmatoare:
public class Car
{
internal readonly ReadOnlyCollection<Component> _components;

public Car(ReadOnlyCollection<Component> components) //sau public Car(List<Component> components)
{
_components = components; //sau _components = components.AsReadOnly();
}
}

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