Radical Documentation
View on GitHub
Primary version
Primary version
  • 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
      • Application configuration
      • Application shutdown
      • Singleton applications
    • AbstractMementoViewModel
      • Simple ViewModel graphs
      • Collections and complex ViewModel graphs
    • Validation and Validation Services
    • Resources
      • Services as resources
      • ViewModels as resources
  • UI Composition
    • UI Composition
      • Region content lifecycle
      • TabControl region
      • Create a custom region
  • Concepts
    • Inversion of Control
      • Third party DI containers
    • 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
      • Property State
  • Behaviors
    • DataGrid Behaviors
    • Password
    • Generic routed event handler to command behavior
    • Overlay adorner
      • Busy status manager
    • TextBox behaviors:
      • Command
      • Auto select
      • DisableUndoManager (.Net 3.5 only)
  • 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 they are used
  • Upgrade guides
    • Radical Presentation 1.x to Radical 2.x for .NET Core
    • Radical 2.0.0 to Radical 2.1.0
Powered by GitBook
On this page
  • Conventions
  • Bootstrap conventions
  • Assembly scanning
  • ExposeServiceAsResource
  • Singletons
  • Spalsh screen
  • Disable auto-boot
  1. Presentation
  2. Application boot process

Application configuration

PreviousApplication boot processNextApplication shutdown

Last updated 3 years ago

The Radical application behavior, the bootstrap and runtime conventions, and the assembly scanning behavior can be be tweaked by accessing the BootstrapConfiguration instance:

public partial class App : Application
{
    public App()
    {
        this.AddRadicalApplication<MainView>(configuration=>
        {
           //use the configration instance
        });
    }
}

Conventions

Conventions can be customized during the application setup phase, for more information about convention refer to the section.

Bootstrap conventions

are designed to configure the Radical application boostrap phase and the IoC/DI setup. Bootstrap conventions customization happens throughout the BootstrapConventions object exposed by the configuration instance.

Assembly scanning

ExposeServiceAsResource

Singletons

Spalsh screen

Disable auto-boot

Radical applications automatically subscribe to the hosting WPF Application lifecycle events to bootstrap the Radical infrastructure. To gain full control over the boot steps use the DisableAutoBoot() configuration option and call Boot() when in need of boostrapping the Radical application.

By default a Radical application scans all the assemblies found in the bin directory and in its subdirectories. It's possible to configure the assembly scanning behavior to customize how types are loaded and used to configure the IoC/DI infrastructure. Refer to the documentation for more information.

Radical registers, during the application boot phase, all dependencies as components in the IoC container. Other components can depend on registered dependencies via DI. There are scenarios when DI is not available, for example when using WPF template selectors, and the code needs a dependency that is registered in the IoC container. For these scenarios, it's possible to expose registered components as resources both at the application level or at the view level. For more information refer to the .

There are cases in which we need that our application cannot be started twice by the user, these applications are called singleton applications. For more information on how to customize the bootstrapp process to handle such cases, refer to the .

Radical has built-in support for splash screens. Refer to the , for more details.

NOTE: When using support DisableAutoBoot() is ignored as the generic host approach already gives full control over the bootstrap process.

conventions
Bootstrap conventions
boot process
Services as Resources documentation
singleton applications documentation
splash screen how to
generic host