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(...

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

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