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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP