This project is read-only.


  1. What is customised object instantiation?
  2. Type aliases
  3. Built in helpers
  4. Developing helpers

What is customised object instantiation?

The standard way of instantiating objects means calling an object's constructor with a series of parameters, i.e. calling an object's ".ctor" method. This can be done with either exoCreate or exoInvoke with ".ctor" as a member name.

The custom object instantiation sub-system (accessed via exoCustomCreate) allows users to easily create a Type and provide initialisation data in a single function call. This is similar to invoking a factory method for a Type.

A few of these factories for the most common .NET types are included in the standard distribution but developers add extensions for their own Types.

Type aliases

Usually object creation requires a user to specify the full name of the type during object creation. This is true for both standard instantiation via exoCreate or custom creation via exoCustomCreate. So when creating an instance of a double, a must specify "System.Double". This requires users to know the full .NET type name of the class they wish to instantiate. To simplify this process an alias registery is provided that associates a name with a .NET type.

For all type aliases see Type Aliases.

Built in helpers

The following common .NET types have built-in custom creation factories:
  1. Value types
  2. Arrays
  3. Lists
  4. Dictionaries
  5. Jagged Arrays
  6. Double Arrays

For more information see Examples.

Developing helpers

Developers can extend the processor pipeline for custom creators to add their own types. Documentation required.

Last edited Apr 16, 2013 at 8:26 PM by Tjaart, version 3


No comments yet.