[ObsoleteAttribute("Use UpdateStarting instead.")]
public event CancelEventHandler ShutdownRequested

<ObsoleteAttribute("Use UpdateStarting instead.")>
Public Event ShutdownRequested As CancelEventHandler

public:
[ObsoleteAttribute(L"Use UpdateStarting instead.")]
 event CancelEventHandler^ ShutdownRequested {
	void add (CancelEventHandler^ value);
	void remove (CancelEventHandler^ value);
}

[<ObsoleteAttribute("Use UpdateStarting instead.")>]
member ShutdownRequested : IEvent<CancelEventHandler,
    CancelEventArgs>

Value

Note: This event is now obsolete. The UpdateStarting event provides additional functionality.

This event is raised whenever the controller needs to shut down its hosting application in order to apply an update. The hosting application is shut down during a call to ApplyUpdate or UpdateInteractive. This event is raised from all UpdateController instances that share the ApplicationId of the UpdateController on which ApplyUpdate was called.

If a handler for this event sets Cancel to , the update will not be applied and ApplyUpdate will return false. If any other controller takes too long to respond, ApplyUpdate will throw an InstanceShutdownException and the update will not be applied. When calling UpdateInteractive, an exception will not be thrown, but the update will not be applied and an error message will be shown to the user.

This method is raised last from the controller that will apply the update, and only if all other controllers did not time out or cancel the event.

When an update is applied using the NoShutdown option, this event is still raised on all instances, but the initiating application will not automatically shut down. The update process can still be cancelled by this event.

Reference