Skip to main content

Cannot serialize member ... because it implements IDictionary

Cat de cunoscuta vi se pare urmatoarea eroare:
Cannot serialize member [FooMember]
... because it implements IDictionary.
Primul lucru pe care oamenii il spun cand intalnesc aceasta eroare este: "Pai logic ca crapa, un dictionar nu e serializabil". Da, intr-o oarecare masura enuntul de mai sus este adevarat, dar nu in totalitate.
Nu toate serializatoarele sunt capabile sa serializeze un IDictionary. Cele mai dese probleme de acest gen apare cand se lucreaza cu XmlSerializer. Trebuie tinut cont ca aceasta problema nu apare la serializare ci la deserializare. Deserializatorul nu stie cu ce obiecte lucreaza, nu gaseste nici o informatie despre tipul lor.
O solutie destul de simpla, care este la indemana oricui este sa folosim DataContractSerializer pentru a serializa/deserializa un dictionar. Schimbariile care trebuie facute pentru a trece de la XmlSerializer la DataContractSerializer sunt destul de putin.
Primul pas este sa marcam clasa pe care o dorim sa o serializam cu DataContract, iar toate elementele pe care dorim sa le serializam cu atributul DataMember. Acest pas nu este obligatoriu pentru .NET 3.5 SP1 +. Daca folositi .NET 3.5 SP1, .NET 4.0 sau .NET 4.5 acest pas este optional. By default tot ce e public se serializare. In cazul in care aveti propietati pe care nu vreti sa le serializati, este nevoie sa adaugati aceste atribute.
Urmatorul pas este sa folosim pentru serializare si deserializare DataContractSerializer, iar metodele Serializer si Deserialize o sa fie inlocuite cu WriteObject si ReadObject.
Mai jos puteti sa gasiti un exemplu de cod in C# 4.5 care poate sa fie folosit pe Windows 8 Metro Style App fara nici o problema:
// Serialize
using (MemoryStream stream = new MemoryStream())
{
DataContractSerializer serializer = new DataContractSerializer(obj.GetType());
using (StreamWriter streamWriter = new StreamWriter(stream, _encoder.Current))
{
using (XmlWriter xmlWriter = XmlWriter.Create(streamWriter))
{
serializer.WriteObject(xmlWriter, obj);
xmlWriter.Flush();
}
stream.Seek(0, SeekOrigin.Begin);
// TODO: save or manipulate streamWriter
}
}
// Deserialize
using (StringReader reader = new StringReader(_encoder.ToString(content)))
{
XmlReader xmlReader = XmlReader.Create(reader);
XmlSerializer serializer = GetSerializer(typeof (TEntity));

return (TEntity) serializer.Deserialize(xmlReader);
}
Daca am fi fost intr-o aplicatie non-metro style am fi putut lucra cu XmlTextWriter unde sa avem propietatea Formatting setata cu valoare Formating.Indented. In acest caz XML generat ar fi fost mult mai usor de citit de catre oameni. Dar putem sa traim fara nici o problema fara aceasta optiune.
Enjoy!

Comments

Popular posts from this blog

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

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

[Post Event] Azure AI Connect, March 2025

On March 13th, I had the opportunity to speak at Azure AI Connect about modern AI architectures.  My session focused on the importance of modernizing cloud systems to efficiently handle the increasing payload generated by AI.