Skip to main content

ReadOnlyDictionary in .NET 4.0 and 4.5

.NET 4.5 aduce destul de multe feature noi. Insa pana o sa fie adoptat pe proiectele in curs o sa treaca o perioada destul de lunga. Unele din aceste feature le putem avea si in .NET 4.0, doar ca trebuie sa scriem putin cod.
In .NET 4.5 daca avem nevoie de un dictionar care sa fie read-only este destul de simplu. Avem la dispozitie interfata IReadOnlyDictionary si implementarea acesteia. Implementarea poate sa fie gasita in namespace-ul System.Collections.Generic din 4.5.
Dictionary<int, string> dictionary = new Dictionary<int, string>();
dictionary.Add(1, "first");
dictionary.Add(2, "second");

ReadOnlyDictionary<string, int> readOnlyDictionary =
new ReadOnlyDictionary<string, int>(dictionary);

Ce este bine de stiut ca operatiile de add/edit/delete inca exista, doar ca in momentul in care acestea o sa fie apelate o sa arunce o exceptie de tip NotSupportedException.
Daca ati lucrat cu API-ul de Team Foundation, ati putut observa ca exista deja o implementare pentru acesta colecție. La fel si in API-ul de la Office 2007.
Daca nu lucram cu API-uri care au deja implementari a unui dictionar read-only, putem sa ne definim noi propia implementare. Tot ce trebuie sa facem este sa implementam interfata IDictionary care sa accepte in constructor un dictionar sau o colectie de elemente . Toate metodele care permit adaugare, modificare sau editare de elemente din dictionar nu trebuie implementate.
O alta varianta este sa va definiti si o interfata de tip IReadOnlyDictionary, care sa permita doar acces la date.
Mai jos puteti sa gasiti o implementare a unui ReadOnlyDictionary, implementand direct interfata IDictionary.
  public class ReadOnlyDictionary<TKey, TValue> : IDictionary<TKey, TValue>
{
private const string NotsupportedExceptionMessage = "This dictionary is read-only";

private readonly IDictionary<TKey, TValue> _dictionary;

public ReadOnlyDictionary(IDictionary<TKey, TValue> dictionary)
{
_dictionary = dictionary;
}

public void Add(TKey key, TValue value)
{
throw new NotSupportedException(NotsupportedExceptionMessage);
}

public bool ContainsKey(TKey key)
{
return _dictionary.ContainsKey(key);
}

public ICollection<TKey> Keys
{
get { return _dictionary.Keys; }
}

public bool TryGetValue(TKey key, out TValue value)
{
return _dictionary.TryGetValue(key, out value);
}

public bool Contains(KeyValuePair<TKey, TValue> item)
{
return _dictionary.Contains(item);
}

public void CopyTo(KeyValuePair<TKey, TValue>[] array, int arrayIndex)
{
_dictionary.CopyTo(array, arrayIndex);
}

public int Count
{
get { return _dictionary.Count; }
}

public bool IsReadOnly
{
get { return true; }
}

public TValue this[TKey key]
{
get
{
return _dictionary[key];
}
set
{
throw new NotSupportedException(NotsupportedExceptionMessage);
}
}

public IEnumerator<KeyValuePair<TKey, TValue>> GetEnumerator()
{
return _dictionary.GetEnumerator();
}

System.Collections.IEnumerator System.Collections.IEnumerable.GetEnumerator()
{
return (_dictionary as System.Collections.IEnumerable).GetEnumerator();
}

public bool Remove(TKey key)
{
throw new NotSupportedException(NotsupportedExceptionMessage);
}

public void Add(KeyValuePair<TKey, TValue> item)
{
throw new NotSupportedException(NotsupportedExceptionMessage);
}

public void Clear()
{
throw new NotSupportedException(NotsupportedExceptionMessage);
}

public bool Remove(KeyValuePair<TKey, TValue> item)
{
throw new NotSupportedException(NotsupportedExceptionMessage);
}

public ICollection<TValue> Values
{
get { throw new NotSupportedException(NotsupportedExceptionMessage); }
}
}


Comments

  1. Interesant - sau cine e mai lenes, va folosi o implementare gata facuta, precum GuardedDictionary din C5 collections: http://www.itu.dk/research/c5/

    ReplyDelete

Post a Comment

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