Object vs Dynamic vs Var and ExpandoObject

using System;
class Program
{
    static void Main(string[] args)
    {
        object iobj = 10; // Perfectly Legal
        var ivar = 10;
        dynamic dvar = 10;
        Console.WriteLine(iobj.GetType()); // Gives System.Int32.
        Console.WriteLine(ivar.GetType()); // Gives System.Int32.
        Console.WriteLine(dvar.GetType()); // Gives System.Int32.
        // 1)
        // iobj = iobj + 10; // Illegal and gives a compile-time error.
        // Reason: At compile time, it is of type object, so the compiler doesn't know how to add object type.
        // You need to cast it to an integer to perform the addition.
        iobj = (int)iobj + 10;
        Console.WriteLine(iobj); // Perfectly legal
        // 2)
        ivar = ivar + 10; // Perfectly legal
        // Reason: At compile time, it is not of type var but int.
        Console.WriteLine(ivar);
        // 3)
        dvar = dvar + 10; // Perfectly legal
        // Reason: At compile time, it is not of type var but int.
        Console.WriteLine(dvar);
        Console.ReadLine();
    }
}

using System;
class Program
{
    static void Main(string[] args)
    {
        // Using var
        // var val = 10; // This would infer the type as int
        // val = "string"; // This line would be illegal, as you cannot assign a string to an int variable.

        // Using dynamic
        dynamic dynam = 10; // Dynamically typed variable
        dynam = "string1"; // Perfectly legal, as the type is determined at runtime
        Console.WriteLine(dynam); // Will print "string1"
        Console.ReadLine();
    }
}

The following is the usage of these two.

Dictionary<string, Control> d = new Dictionary<string, Control>();

That can now be written simply as.

var dictionary1 = new Dictionary<string, Control>();
dynamic dynamicDictionary = new Dictionary<string, Control>();

Difference between object and dynamic

Dynamic tells the compiler that the data type can be anything, so the compiler doesn't interfere, and dynamic gives no compile-time error but will definitely give a runtime error if all is not good (in other words, runtime error.

The following code will work properly for dynamic, but not if the dynamic is replaced by the object. (The reason is explained in the preceding object-type discussion.

dynamic dyn = 10.0;  // Assigning a double value to dyn
dyn = dyn + 10;      // Adding 10 to dyn (now dyn is 20.0)
dyn = "10";          // Assigning a string value to dyn
dyn = dyn + 10;      // Attempting to add 10 to a string (results in a runtime error)

So if Dynamic can take any data type, can we pass it to another function expecting something other data type and crash.

Assume we have a function.

public static void display(string abc)
{
    Console.WriteLine(abc);
}

Now we have.

object iobj = 10;
display(iobj);
dynamic dynam = 10;
display(dynam);
Console.ReadLine();

Here, the first one will not compile, and the second one will compile but give a runtime error.

What is Dynamic Suppresses the Compiler Logic

With the dynamic keyword, one interesting object comes out to be ExpandoObject.

In order to emulate the dynamic functionality of adding members to objects at runtime, .Net comes with the IDynamicMetaObjectProvider interface. Classes implementing it will have a full dynamic behavior.

A useful class in version 4 of the .NET Framework is ExpandoObject. It is a built-in implementation of the IDynamicMetaObjectProvider interface and it allows dynamically adding members at runtime, like in the following example.

dynamic contact = new ExpandoObject();
contact.Name = "GOGO";
contact.Phone = "206-555-0144";
contact.Address = new ExpandoObject(); // Notice this line
contact.Address.Street = "Main St";

The code is taken from MSDN. This has the following two interesting features.

dynamic contact = new ExpandoObject();
contact.Name = "GOGO";
contact.Phone = "206-555-0144";
// Adding another node (e.g., contact.Address) without explicitly creating a new ExpandoObject
contact.Address = new ExpandoObject();
contact.Address.Street = "Main St";
contact.Address.City = "Exampleville";

• They are used to reduce the number of lines of code. We do not need to write the type name again and again.
  • They are used extensively in anonymous methods. You wouldn't be able to declare a variable of an anonymous type if you always need to include the type name as part of the variable declaration.
  • COM interop.
  • Reading XML, JSON without creating custom classes.