Skip to main content

DataContractSerializer and list of abstract class

Plecam de la urmatoarea structura:
public abstract class BaseCar
{
public string Name { get; set; }
}
public class SportCar : BaseCar { }
public class UtilityCar : BaseCar { }
public Foo
{
public Foo()
{
Cars = new List<BaseCar>();
}
public List<BaseCar> Cars { get; set; }
}
...
Foo myFoo = new Foo();
myFoo.Cars.Add( new SportCar());
DataContractSerializer serializer = new DataContractSerializer(typeof(Foo));
serializer.WriteObject(myXmlWriter, myFoo);
Cand nu avem specificat nici un atribut de tip DataContract, toate campurile care sunt publice se serializeaza. In cazul nostru codul se compileaza fara probleme si obtinem un obiect serializat. Problema apare cand vrem sa deserializam obiectul nostru si ne trezim ca proprietatea Cars este null. Chiar daca in constructor inializam aceasta proprietate obtinem in continuare NULL.
Cand ne uitam peste cod realizam ca lucram cu o clasa abstracta, iar in acest caz avem nevoie de atributul KnownTypes pe care il si adaugam sub forma:
[KnownTypes(typeof(SportCar))]
[KnownTypes(typeof(UtilityCar))]
clasei Foo. Cand testam din nou aplicatia nici o schimbare. Daca problema ar fi fost de la KnownTypes, am fi obtinut o eroare specifica care ne spune ca nu se poate serializa/deserializa.
Totusi problema persista si ne horaram sa specificam explicit ce proprietati vrem sa serializam. Clasele noastre ajung sa aibe urmatoarea forma:
[DataContract]
public abstract class BaseCar
{
[DataMember]
public string Name { get; set; }
}
[DataContract]
public class SportCar : BaseCar { }
[DataContract]
public class UtilityCar : BaseCar { }
[KnownTypes(typeof(SportCar))]
[KnownTypes(typeof(UtilityCar))]
[DataContract]
public Foo
{
public Foo()
{
Cars = new List<BaseCar>();
}
[DataMember]
public List<BaseCar> Cars { get; set; }
}
Rulam din nu codul si observam ca acuma totul functioneaza fara nici o problema. Lista noastra de masini este serializata si deserializata fara nici o problema. Am incercat sa caut pe MSDN o locatie unde sa ni se precizeze ca trebuie explicit sa folosim aceste doua atribute cand avem lista de clase abstracte, dar din pacate nu am gasit. Am fost directionat de catre un coleg in urmatoarea locatie unde sunt enumerate regulile deja cunoscute, dar despre acest comportament nu era specificat nimica. http://msdn.microsoft.com/en-us/library/cc656732%28v=vs.100%29.aspx

Comments

  1. Daca tipurile nu sunt abstracte, nu apare problema?
    (sunt o gramada de reguli pentru serializarea colectiilor, da..: http://msdn.microsoft.com/en-us/library/aa347850.aspx )

    ReplyDelete
    Replies
    1. Doar daca avem clase abstracte apare problema.

      Delete

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