Tidbits on software development, technology, and other geeky stuff.

Complex Types in Entity Framework (Code First)

Last week I gave a tech talk on Entity Framework. One of the questions that was asked at the end of the talk was how to handle “complex types”.   That is, how to get Entity Framework to map data into a container “child object” correctly.  A couple of reasons you might want to do this are: to organize your model classes in a cleaner way and also to isolate data for serialization.  For example, if you have a database table called Person that includes address related fields, you might want to create an Address class and have EF map just the address fields in this type.  This gives you flexibility so that, for example, you could serialize the address info to JSON without having to ‘ignore’ a bunch of other fields you don’t want serialized.

I had to dig around a bit to figure out how to get it to work but it is definitely possible.  You just need to:

The article Associations in EF Code First CTP5: Part 1 – Complex Types was definitely helpful with understanding this.

Here is a gist demonstrating what it looks like.


public class Person {
  public string FirstName {get;set;}
  public string LastName  {get;set;}
  public Address = new Address();   // << It's important to instantiate Address.

[ComplexType]  // <<  This attribute is important.
public class Address {
  public string Address1 {get;set;}
  public string Address2 {get;set;}
  public string City {get;set;}

/*Example usage:
   Person p = new Person();
   p.Address.Address1 = "1848 Willow Drive";
   p.Address.Address2 = "Unit 105";
   p.Address.Address1 = "Houston";

/*  Table structure
      FirstName varchar(50),
      LastName varchar(50),
      Address1 varchar(50),
      Address2 varchar(50),
      City varchar(50)

Discuss on Twitter