This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

// Create a type dynamically.

public class Program

{

static void Main(string[] args)

{

Console.WriteLine("***** Fun with Late Binding *****");

// Try to load a local copy of CarLibrary.

Assembly a = null;

try

{

a = Assembly.Load("CarLibrary");

}

catch(FileNotFoundException e)

{

Console.WriteLine(e.Message);

return;

}

// Get metadata for the Minivan type.

Type miniVan = a.GetType("CarLibrary.MiniVan");

// Create the Minivan on the fly.

object obj = Activator.CreateInstance(miniVan);

Console.WriteLine("Created a {0} using late binding!", obj);

Console.ReadLine();

}

}

Notice that the Activator.CreateInstance() method returns a System.Object rather than a

strongly typed MiniVan. Therefore, if you apply the dot operator on the obj variable, you will fail to

see any members of the MiniVan type. At first glance, you may assume you can remedy this problem

with an explicit cast; however, this program has no clue what a MiniVan is in the first place (and if

you did, why use late binding at all)!

Remember that the whole point of late binding is to create instances of objects for which there

is no compile-time knowledge. Given this, how can you invoke the underlying methods of the

MiniVan object stored in the System.Object variable? The answer, of course, is by using reflection.