Autogenerated Services

Overview

The XML configuration file has two elements autoService and autoServiceCustom to configure bindings for interfaces, for which the implementations are auto-generated.

Element autoService allows specifying interface implementation completely in configuration. Element autoServiceCustom allows specifying an implementation of interface IoC.Configuration.ConfigurationFile.ICustomAutoServiceCodeGenerator in child element autoServiceCodeGenerator that generates the implementation of autogenerated interface implementation.

Element autoService is easier to setup, however autoServiceCustom allows more control over the generated implementation. The motivation for adding autoServiceCustom was to provide auto-implemented interface implementations based on C# attributes applied to interfaces and interface methods and properties.

Elements autoService and autoServiceCustom can appear in any order under iocConfiguration/dependencyInjection/autoGeneratedServices and iocConfiguration/pluginsSetup/pluginSetup/dependencyInjection/autoGeneratedServices elements.

• Element autoService
  • Overview
    • Explanation of autoMethod for method IActionValidatorFactory.GetValidators(…) above
    • Some notes:
    • Using auto-generated implementation
      • Element autoMethod
        • The format of autoMethod
          • Method name and return type in autoMethod
          • Method signature
          • Specifying the return values
          • Referencing the auto-implemented method parameters
          • Caching the returned values
          • Resolving conflicts by using declaringInterface in autoMethod
      • Element autoProperty
        • The Format of autoProperty
          • Property name and return type in autoProperty
          • Specifying the returned value
          • Example:
          • Resolving conflicts by using declaringInterface in autoProperty
• Element autoServiceCustom