The reporting mechanism allows creating a full report of the bootstrapping process. To be able to report the bootstrapping process the process must actually run and a reporter must be present. By default the bootstrapper uses a null reporter which … Continue reading →

Configuration sections The bootstrapper supports loading of configuration sections through behaviors. The behaviors responsible for loading configuration sections must be applied in the begin section of the run syntax. ConfigurationSection To be able to load configuration sections the ConfigurationSectionBehavior must … Continue reading →

Strategy The strategy defines the order of execution for extension points and behaviors. The custom strategy must inherit from IStrategy. For convenience, use the provided abstract base class AbstractStrategy{TExtension} which simplifies defining a custom strategy. The strategy could look like … Continue reading →

Behaviors Behaviors allow extending the bootstrapping process in an aspect oriented style. Behaviors gain access to extensions which are participating in the bootstrapper process and can therefore influence them for example by injecting additional runtime information into an extension. Behaviors … Continue reading →

Introduction To get started with the bootstrapper you need the following three things: Extension interface Strategy Bootstrapper setup Extension interface The extension interface defines the extension points which are called by the bootstrapper. The custom extension interface must inherit from … Continue reading →