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
  1. Presentation
  2. Application boot process

Application shutdown

In order to shutdown an application built using Radical there are 3 main options.

Canonical WPF way: App.Current.Shutdown();

There is no reason to not use the default WPF standard way to shutdown the application, the only thing we cannot do in this case is to prevent the shutdown process to complete, we have no control over it.

When the App.Current.Shutdown() method is called the bootstrapper raises, via the message broker, the following event:

  • ApplicationShutdown: that simply notifies to the application that is shutting down;

2 way shutdown via RadicalApplication.Shutdown();

If we need an option to cancel the application shutdown process we should use the Shutdown() method exposed by the RadicalApplication. In this way the following events are broadcasted/dispatched by the message broker:

  1. ApplicationShutdownRequested is dispatched synchronously to the application and has a Cancel property that can be set to true to cancel the shutdown process;

  2. ApplicationShutdownCanceled is broadcasted whenever the shutdown process is cancelled;

  3. ApplicationShutdown is finally dispatched asynchronously to notify to the application that is shutting down;

To get an instance of the current RadicalApplication the following snippet can be used:

public partial class App : Application
{
    public App()
    {
        var radicalApplication = this.AddRadicalApplication<Presentation.MainView>();
    }
}

NOTE: the current RadicalApplication is not registered in the IoC container.

2 way shutdown via ApplicationShutdownRequest message

Exactly the same approach as above can be obtained broadcasting, via the message broker, the ApplicationShutdownRequest message, without the need to have a reference to the current radical application.

PreviousApplication configurationNextSingleton applications

Last updated 3 years ago