MCS provides a markup language that allows authors to define the structure of their own components. The intent behind defining the structure of custom components is to enable the automatic binding of component instances based on both their structural relationship as well as their types. During the process of binding the components are validated on the server-side to ensure that the component structure is valid before it is run on the client. The validation mechanism uses whatever information is provided in the component classes to detect as many logical errors it can. Refer to the topics entitled Component types and classes and Validation for details.
MCS provides a markup language that allows authors to define the structure of their own components. The intent behind defining the structure of custom components is to enable the automatic binding of component instances based on both their structural relationship as well as their types. During the process of binding the components are validated on the server-side to ensure that the component structure is valid before it is run on the client. The validation mechanism uses whatever information is provided in the component classes to detect as many logical errors it can. Refer to the topics entitled Component types and classes and Validation for details.
Custom components are not supported on WML devices.