The central interface to Spring.NET's IoC container.
For a list of all members of this type, see IApplicationContext Members .
|AbstractApplicationContext||Partial implementation of the IApplicationContext interface.|
|AbstractXmlApplicationContext||Convenient abstract superclass for IApplicationContext implementations that draw their configuration from XML documents containing object definitions as understood by an XmlObjectDefinitionReader.|
|GenericApplicationContext||Generic ApplicationContext implementation that holds a single internal DefaultListableObjectFactory instance and does not assume a specific object definition format.|
|StaticApplicationContext||IApplicationContext that allows concrete registration of objects and messages in code, rather than from external configuration sources.|
|WebApplicationContext||Web application context, taking the context definition files from the file system or from URLs. Treats resource paths as web resources, when using IApplicationContext.GetResource. Resource paths are considered relative to the virtual directory. Note: In case of multiple config locations, later object definitions will override ones defined in earlier loaded files. This can be leveraged to deliberately override certain object definitions via an extra XML file.|
|XmlApplicationContext||An IApplicationContext implementation that reads context definitions from XML based resources.|
IApplicationContext implementations provide:
In addition to standard object factory lifecycle capabilities, IApplicationContext implementations need to detect IApplicationContextAware, IEventRegistryAware, and IMessageSourceAware objects and supply their attendant dependencies accordingly.
This interface is the central client interface in Spring.NET's IoC container implementation. As such it does inherit a quite sizeable number of interfaces; implementations are strongly encouraged to use composition to satisfy each of the inherited interfaces (where appropriate of course).
Assembly: Spring.Core (in Spring.Core.dll)