Advanced Registration Techniques

In this article we'll cover the more advanced registration techniques and how/when to use them. If you are looking for how to register a component or have not yet read How to register a component we strongly encourage you to do so first.

The IOC container comes with more than just the ability to register a component. There's a lot of flexibility built in that we will cover in this article. This mainly evolves around the configuration files itself rather than capabilities of the IOC container when registering components and patching properties.

Including associated files

You may include other configuration files in case you are interested in splitting up the files. This is done relatively to the configuration file you have. Like so:

    
    
    <configuration>
    
         <!-- Include a config file in the same folder -->
    	<include uri="samefolder.config" />
    
    	<!-- Include a file in a folder next to the folder you're already in -->
    	<include uri="../siblingfolder/differentfolderfile.config" />
    
    </configuration>
    
    

Include an entire folder

You can also include entire folders (and it's subfolders) with the following syntax

    
    
    	<!-- include an entire folder -->
    	<include-folder path="../Apps" />
    
    

Please note that all configuration files from sub folders will be recursively included as well.

Swtich folders on/off

When you include folders you can disable them by suffixing them with .disabled - In that case they will not be included recursively. This works on the root level as well, which means they will be ignored completely. This is in particular useful if you need to turn apps off from the apps folder completely.

Disable config files

Just like it is possible to ignore folders you can also turn off configuration files placed under the apps folder. Simply suffix them with .disabled or .example to make sure the IO does not pick them up.