Describes an object that can resolve messages.
For a list of all members of this type, see IMessageSource Members .
|AbstractApplicationContext||Partial implementation of the IApplicationContext interface.|
|AbstractMessageSource||Abstract implementation of the IHierarchicalMessageSource interface, implementing common handling of message variants, making it easy to implement a specific strategy for a concrete IMessageSource.|
|AbstractXmlApplicationContext||Convenient abstract superclass for IApplicationContext implementations that draw their configuration from XML documents containing object definitions as understood by an XmlObjectDefinitionReader.|
|DelegatingMessageSource||Empty IMessageSource implementation that simply delegates all method calls to it's parent IMessageSource.|
|GenericApplicationContext||Generic ApplicationContext implementation that holds a single internal DefaultListableObjectFactory instance and does not assume a specific object definition format.|
|NullMessageSource||An IMessageSource that doesn't do a whole lot.|
|ResourceSetMessageSource||An IMessageSource implementation that accesses resources from .resx / .resource files.|
|StaticApplicationContext||IApplicationContext that allows concrete registration of objects and messages in code, rather than from external configuration sources.|
|StaticMessageSource||Simple implementation of IMessageSource that allows messages to be held in an object and added programmatically.|
|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.|
This enables the parameterization and internationalization of messages.
Spring.NET provides one out-of-the-box implementation for production use:
Assembly: Spring.Core (in Spring.Core.dll)