Dynamic in C# 4.0: Introducing the ExpandoObject

Dynamic in C# 4.0: Introducing the ExpandoObject

Rate This
  • Comments 73

You have probably already heard about the new dynamic feature in C# 4.0 and how it is used to support COM interop. If you haven't, I strongly recommend reading the following MSDN articles: Using Type dynamic and How to: Access Office Interop Objects by Using Visual C# 2010 Features.

Well, where else can you use this new feature? What are the use cases? Where does dynamic dispatch work better than static typing?

The quick answer is that whenever you see syntax like myobject.GetProperty("Address"), you have a use case for dynamic objects. First of all, the above syntax is difficult to read. Second, you don’t have any IntelliSense support for the property name, and if the “Address” property doesn’t exist you get a run-time exception. So why not create a dynamic object that calls the property as myobject.Address? You still get the run-time exception, and you still don't get IntelliSense, but at least the syntax is much better.

In fact, it’s not just better syntax. You also get flexibility. To demonstrate this flexibility, let’s move to ExpandoObject, which is a part of the new dynamic language runtime (DLR). ExpandoObject instances can add and remove members at run time. Where can you use such an object? XML is a good candidate here.

Here’s a code example that I took from MSDN. (Yes, I am an MSDN writer myself, so I use MSDN a lot.)

XElement contactXML =
    new XElement("Contact",
        new XElement("Name", "Patrick Hines"),
        new XElement("Phone", "206-555-0144"),
        new XElement("Address",
            new XElement("Street1", "123 Main St"),
            new XElement("City", "Mercer Island"),
            new XElement("State", "WA"),
            new XElement("Postal", "68042")

Although LINQ to XML is a good technology and I really love it, those new XElement parts look a little bit annoying. This is how I can rewrite it by using ExpandoObject.

dynamic contact = new ExpandoObject();
contact.Name = "Patrick Hines";
contact.Phone = "206-555-0144";
contact.Address = new ExpandoObject();
contact.Address.Street = "123 Main St";
contact.Address.City = "Mercer Island";
contact.Address.State = "WA";
contact.Address.Postal = "68402";

Just note a couple of things. First, look at the declaration of contact.

dynamic contact = new ExpandoObject();

I didn’t write ExpandoObject contact = new ExpandoObject(), because if I did contact would be a statically-typed object of the ExpandoObject type. And of course, statically-typed variables cannot add members at run time. So I used the new dynamic keyword instead of a type declaration, and since ExpandoObject supports dynamic operations, the code works.

Second, notice that every time I needed a node to have subnodes, I simply created a new instance of ExpandoObject as a member of the contact object.

It looks like the ExpandoObject example has more code, but it’s actually easier to read. You can clearly see what subnodes each node contains, and you don’t need to deal with the parentheses and indentation. But the best part is how you can access the elements now.

This is the code you need to print the State field in LINQ to XML.


And this is how it looks with ExpandoObject.


But what if you want to have several Contact nodes? Like in the following LINQ to XML example.

XElement contactsXML =
    new XElement("Contacts",
        new XElement("Contact",
            new XElement("Name", "Patrick Hines"),
            new XElement("Phone", "206-555-0144")
        new XElement("Contact",
            new XElement("Name", "Ellen Adams"),
            new XElement("Phone", "206-555-0155")

Just use a collection of dynamic objects.

dynamic contacts = new List<dynamic>();

contacts.Add(new ExpandoObject());
contacts[0].Name = "Patrick Hines";
contacts[0].Phone = "206-555-0144";

contacts.Add(new ExpandoObject());
contacts[1].Name = "Ellen Adams";
contacts[1].Phone = "206-555-0155";

Technically speaking, I could write dynamic contacts = new List<ExpandoObject>() and the example would work. However, there are some situations where this could cause problems, because the actual type of the list elements should be dynamic and not ExpandoObject, and these are two different types. (Once again, references to the ExpandoObject objects are statically-typed and do not support dynamic operations.)

Now, if you want to find all the names in your contact list, just iterate over the collection.

foreach (var c in contacts)

Again, this syntax is better than LINQ to XML version.

foreach (var c in contactsXML.Descendants("Name"))

So far, so good. But one of the main advantages of LINQ to XML is, well, LINQ. How would you query dynamic objects? Although there is still a lot to be done in this particular area, you can query dynamic objects. For example, let’s find all the phone numbers for the specified name.

var phones = from c in (contacts as List<dynamic>)
             where c.Name == "Patrick Hines"
             select c.Phone;

True, the cast here doesn’t look like something strictly necessary. Certainly the compiler could have determined at run-time that contacts is List<dynamic>. But as I said, there is still some work to be done in this area.

Another thing to note is that this trick works only for the LINQ to Objects provider. To use dynamic objects in LINQ to SQL or other LINQ providers, you need to modify the providers themselves, and that’s a completely different story.

However, even with the cast, syntax is still better than in a LINQ to XML query.

var phonesXML = from c in contactsXML.Elements("Contact")
                where c.Element("Name").Value == "Patrick Hines"
                select c.Element("Phone").Value;

Sure, there are some things that look better in LINQ to XML. For example, if you want to delete a phone number for all the contacts, you can write just one line of code in LINQ to XML.


Since C# doesn’t have syntax for removing object members, you don’t have an elegant solution here. But ExpandoObject implements IDictionary<String, Object> to maintain its list of members, and you can delete a member by deleting a key-value pair.

foreach (var person in contacts)
    ((IDictionary<String, Object>)person).Remove("Phone");

There are other useful methods in LINQ to XML like Save() and Load(). For ExpandoObject you need to write such methods yourself, but probably only once. Here, casting to the IDictionary interface can help as well.

And although I’ve been comparing LINQ to XML and ExpandoObject in this post, these two approaches are not “rivals”. You can convert ExpandoObject to XElement and vice versa. For example, this is what the ExpandoObject to XElement conversion might look like.

private static XElement expandoToXML(dynamic node, String nodeName)
    XElement xmlNode = new XElement(nodeName);

    foreach (var property in (IDictionary<String, Object>)node)

        if (property.Value.GetType() == typeof(ExpandoObject))
            xmlNode.Add(expandoToXML(property.Value, property.Key));

            if (property.Value.GetType() == typeof(List<dynamic>))
                foreach (var element in (List<dynamic>)property.Value)
                    xmlNode.Add(expandoToXML(element, property.Key));
                xmlNode.Add(new XElement(property.Key, property.Value));
    return xmlNode;

This little trick might help you access all the LINQ to XML functions when you need them but at the same time use more convenient syntax when creating and modifying XML trees.

Of course, XML is not the only area where you can use ExpandoObject. If you heavily use reflection or work a lot with script objects, you can simplify your code with ExpandoObject. On the other hand, ExpandoObject is not the only useful class that the DLR provides. The DynamicObject class, for example, enables you to take more control over dynamic operations and define what actually happens when you access a member or invoke a method. But that’s a topic for another blog post.

One more thing to note is that libraries that look up members by name might someday adopt the DLR and implement the IDynamicMetaObjectProvider interface. (This interface actually provides all the “magic” – or dynamic dispatch – for ExpandoObject and the dynamic feature in general.) For example, if LINQ to XML implements this interface, you would be able to write dynamic contacts = new XmlElement() instead of dynamic contacts = new ExpandoObject() and perform the same operations that I have shown in the examples for the ExpandoObject type.

All the examples provided in this blog post work in Visual Studio 2010 Beta 1. If you have any comments or suggestions, you are welcome to post them here or contact the DLR team at http://www.codeplex.com/dlr. You can also write an e-mail to the DLR team at dlr@microsoft.com.


See how you can improve this example in my next post: Dynamic in C# 4.0: Creating Wrappers with DynamicObject.

Leave a Comment
  • Please add 2 and 3 and type the answer here:
  • Post
  • Could be very usefull, especially if you don't like coding much. Very flexible. But still agree with some comments, which say that it can bring a lot of errors.

  • Yup. Seen that for years in Adobe Flex. But it's just called object().

  • Would this work in the current implementation ?

    contact.Address = new ExpandoObject().Street = "123 Main St";

  • @ D0cNet

    No, this is not supported. It's important to understand that dynamic feature cannot support syntax that C# language does not support. For example, some languages have syntax like "delete obj.Member", but C# does not have this syntax, and so you simply can't write such a code, no matter whether you use dynamic or statically-typed objects.

    The same is here: C# does not allow you to call methods on constructors, neither for statically-typed objects, nor for dynamic ones.

  • Syntactic sugar and RTEs instead of compile errors?  If my code never reaches a production environment, fine.  Otherwise, no way in hell.  I've not been pleased with the way the framework has been headed since 3.0 came out, and even that was half crap.

  • Looks great, and I now understand it.. but I am on the fence about it.  Thanks for the writeup for sure

  • Adobe's Actionscript language has slowly been moving away from expando objects to strongly typed code (for performance reasons mainly). Why is C# moving in the other direction?!

    I want strongly typed ECMAScript, not loosely typed C# ;-)

  • I have come o truly *love* LINQ to Objects,  LINQ to XML, and other goodies from C#3.0 like implicit [static] typing, and anonymous types (which are still static but inherently more less restricted to a small, immediate scope limiting risk).

    Having started to get a little deeper into Javascript I'm finally 'getting' the dynamic/prototyping paradigm, but I fear mixing it in with C# will be a real can of worms.

    Perhaps it would be best to simply create a .NET assembly using one of the other languages more natively intended for this, and use it from your C# assemblies rather than possibly ruining C# by trying to throw in everything but the kitchen sink.

  • What I always disliked about the myobject.GetProperty("Address") solution was that you don't have any Intellisense-support and often have to look up the properties names (typing errors included).

    Is there any chance that there will be Intellisense-support for this in the future?

  • @ Matthias

    I am not aware of such a feature right now. I usually advise people to file their suggestions about new features at http://connect.microsoft.com/.

  • Someone can shoot himself in the hand with a nailgun, but that doesn't mean it isn't worthwhile technology, and superior to a hammer for certain applications.

    I appreciate the C# team assuming it's customers are, by and large, responsible professionals.  No nanny state, please.

  • why would anyone need to have methods added at run time? why not just add them to the class definition when programming it, you know that something might be needed before compiling, so may as well do it the simpler way.

  • Matt Warren said:


    Dynamic in C# is primarily to enable C# programs to interoperate better with API's and object models defined in dynamic languages, without which you would be force to write very difficult to understand code, where the meaning gets lost in the mechanics.


    I think he hit the nail on the head for most software development scenarios (e.g. 'business software', etc. - on the other hand if you're doing 'fun coding' or 'inventive coding', maybe you could find a use for this).

    So in short, IMO if you're doing standard professional development and think you have this sort of use for the Expando object, my strong recommendation would be to take a really hard look at why you're doing it.  1) if it's for the 'coolness' factor, you (and presumably your job security) are probably better off without 2) 'kick it up a level' and see if a different design could obviate the situation in which it proves useful.  Again, my humble opinion.

  • Hohoho, people, have You ever heard about PHP ?

    This kind of construction is pretty old there. Sample:


    $obj = null;

    $obj->Val_a = 1;

    $obj->Val_b = 'test';

    echo $obj->Val_b,'#',$obj->Val_a;

    // output is  test#1


  • Can you serialize and deserialize dynamic objects?

Page 4 of 5 (73 items) 12345