Radical Documentation
View on GitHub
release-1
release-1
  • Home
  • Presentation
    • AbstractViewModel
    • Conventions
      • Bootstrap Conventions
      • Runtime Conventions
      • Conventions override
    • Commands and DelegateCommand
    • IViewResolver
      • Default view behaviors
      • view life cycle events
        • Callback expectations
        • notify messages
    • Message broker MVVM built-in messages
    • Application boot process demystified
      • Application shutdown
      • Singleton applications
    • AbstractMementoViewModel
      • Simple ViewModel graphs
      • Collections and complex ViewModel graphs
    • Validation and Validation Services
  • UI Composition
    • UI Composition
      • Region content lifecycle
      • TabControl region
      • Create a custom region
  • Concepts
    • Inversion of Control
      • Castle Windsor
      • Autofac
      • Unity (v2 & v3)
      • Puzzle Container
    • Entities
      • Property System
    • Messaging and Message Broker
      • POCO messages
      • Standalone message handlers
    • Observers
      • PropertyObserver
      • MementoObserver
      • BrokerObserver
  • Memento
    • Change Tracking Service
      • MementoEntity and MementoEntityCollection
      • Handling change tracking:
        • Simple model
        • Collections
        • Complex objects graph
      • Atomic operations
      • Change Tracking Service API
      • Property Metadata for the ChangeTrackingService
      • Handling collection sync
  • Behaviors
    • DataGrid Behaviors
    • Password
    • Generic routed event handler to command behavior
    • Overlay adorner
      • Busy status manager
    • TextBox behaviors:
      • Command
      • Auto select
      • DisableUndoManager
  • Markup Extensions
    • Editor binding
    • Auto Command binding
  • How to
    • Get the view of a given view model
    • Bi-directional communication between different windows/views
    • Handle the busy status during async/long running operations
    • Implement a customer improvement program
    • Manage focus
    • Create a splash screen
    • Access view model after view is closed
    • Intercept ViewModels before it's used
Powered by GitBook
On this page
  1. Concepts
  2. Inversion of Control

Castle Windsor

PreviousInversion of ControlNextAutofac

Last updated 5 years ago

As we have already seen in the [[quick start|Quick Start (WPF)]] we provide a default implementation of the IoC support using Castle Windsor as IoC container, this implementation is pluggable and completely based on conventions meaning that in most cases you do not need to interact directly with Windsor.

In order to setup the applications using Windsor it’s enough to add a reference to Radical.Windows.Presentation.CastleWindsor via and configure the application like in the following snippet:

public partial class App : Application
{
    public App()
    {
        var bootstrapper = new WindsorApplicationBootstrapper<MainView>();
    }
}

In the case you need to register your own components in Windsor and the provided Bootstrap conventions does not satisfies your requirements you can leverage the power of Windsor Installers and MEF, drop a class like the following in your assembly:

[Export( typeof( IWindsorInstaller ) )]
public class DefaultInstaller : IWindsorInstaller
{
    public void Install( IWindsorContainer container, IConfigurationStore store )
    {
        //register your components here
    }
}

your installer will be automatically wired up at boot time by the infrastructure.

if, for some reason, in your components you need a dependency on the container you can add a dependency directly on IWindsorContainer or on the lightweight IServiceProvider, they are both automatically registered as singleton at boot time.

nuget