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

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

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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