This event is raised by something that wants to force the application to quit.
More...
Client code sometimes needs to force the application to quit. This can be for a variety of reasons, but if the client code simply kills the application or forces the main event loop to stop, the application may not have an opportunity to properly perform some last minute processing, such as saving a project file.
A ShutdownEvent notification is only raised after the main event loop has finished, whereas a ForcedShutdownEvent notification would be raised at the point where the need to quit has been identified. This might be before the main event loop has even started, it could be within the main event loop, or it could be from a separate thread entirely. In addition, ForcedShutdownEvent notifications carry information about why the forced shutdown has been requested. This gives the application the opportunity to provide the user with some explanation as to why the application is shutting down.
This event is intended to be raised on the GlobalNotifications singleton. While it could also be raised on other Observable objects, such usage is discouraged.