Adapter Binding

Together with the AdapterMapping binding available in the mapping file, a more complex form of binding is possible via adapters. There are situations in which a binding (may be field, event or command related) does not depend simply on a one to one relationship between a logical entity and a physical one. For example, if a binding needs to be established between a single logical field representing a full name and two controls representing the first and the last name, the standard mapping capabilities will not suffice.

In this case it is possible to configure a more complex form of adapter binding, where an adapter binds to a number of inputs and outputs simultaneously.

A mapping file contains Adapter references that allow mapping short adapter names to fully qualified paths. These are mapped to the classes implementing these adapters. For more information about Adapters, see Adapters.

It is possible to set up automatic type conversion capabilities between the logical and the physical fields. This is done internally through the usage of TypeConverter classes, stemming from the .NET standard interface System.ComponentModel.TypeConverter. By default, MCE exposes the functionality to automatically convert all the standard .NET types.


Show: