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

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.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…