Namespace Dapplo.Addons

Classes

ModuleAttribute

This is the Module attribute which can be used to specify type-safe meta-data Currently there are none in here, but it was made available so it's possible to add them at a later time In general it is bad to import via a specific type, always try to use contract interfaces. As the IModule is pretty much only a marker interface, it is not very usefull and this is why the attribute is abstract

ShutdownActionAttribute

This is the attribute for a IShutdownModule module

StartupActionAttribute

This is the attribute for a IStartupModule module

StartupException

If this exception is thrown by an startup action, the startup of your application will be terminated. A prerequisite is that your class has the StartupActionAttribute where AwaitStart is true (this is default)

Interfaces

IAction

The IAction describes modules that execute (Currently unused.)

IApplicationBootstrapper

Interface for the ApplicationBootstrapper

IAsyncShutdownAction

The IAsyncShutdownAction describes modules that are called on shutdown

IAsyncStartupAction

The IAsyncStartupAction is an interface for modules that can be started when the application starts Extend you module with this interface, and use the StartupActionAttribute to annotate the module

IBootstrapper

This is the interface for all bootstrappers

IDependencyProvider

This describes something which can provide dependencies

IMefServiceLocator

This interface is one of many which the Dapplo.Addon CompositionBootstrapper (ApplicationBootstrapper) implements. The Bootstrapper will automatically export itself as IMefServiceLocator, so framework code can use imports to get basic servicelocator support. A IMefServiceLocator should only be used for cases where a simple import can't work.

IModule

Basic interface which every module should implement

IServiceExporter

This interface is one of many which the Dapplo.Addon CompositionBootstrapper (ApplicationBootstrapper) implements. The Bootstrapper will automatically export itself as IServiceExporter, so framework code can specify what exports are available A IServiceExporter should only be used for cases where a simple export can't work.

IServiceRepository

This interface is one of many which the Dapplo.Addon CompositionBootstrapper (ApplicationBootstrapper) implements. The Bootstrapper will automatically export itself as IServiceRepository, so framework code can dlls and assemblies A IServiceRepository should only be used for cases where assemblies need to be scanned or exported