Navigation (Windsor)¶

• Main Page
• Main Page (root)
  

• Random Page
• Create a new Page
• All Pages
• Categories
• Navigation Paths
  

• Administration
• File Management
  

• Create Account
  

• Missing pages
  

Search the wiki
»

This documentation is a work in progress.¶

Let us know if some information is not clear, inaccurate or missing. Also feel free to update the wiki yourself.

Registering Installers

Default way of registering components in Windsor is its Fluent Registration API encapsulated in Installers. However to break compile-time dependency on your composition root assembly, you may not have hard reference to some of your assemblies containing your installers. In this case, you can point Windsor to the installers via XML config.

container.Install(Configuration.FromAppConfig());

Installers - registering type¶

You register installers via <install/> element within <installers/> section.

<installers>
   <install type="Acme.Crm.Infrastructure.ServicesInstaller, Acme.Crm.Infrastructure"/>
</installers>

Installers - registering assembly¶

Alternatively you may point Windsor to an assembly, and it will scan the assembly for installers and use all of them as if they were registered one by one.

<installers>
   <install assembly="Acme.Crm.Infrastructure"/>
</installers>

Installers - registering multiple assemblies from given directory¶

Alternatively you may point Windsor to a directory, and it will scan the directory for assemblies and then each assembly for installers and use all of them as if they were registered one by one.

<installers>
   <install directory="extensions" fileMask="Acme.*.dll" publicKeyToken="b77a5c561934e089" />
</installers>

Directory can be absolute or relative. Optionally you can narrow down the scope of assemblies to scan by specifying fileMask for assembly file names, and publicKeyToken to only scam assemblies signed with key identified by the token.