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(

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