ForceApplicationShutdown and ForceTargetApplicationShutdown

MVP

1) If an application is in use when an upgrade is attempted, will the Add-AppXPackage complete or fail?  If so is there any thought of adding the command to a pending queue to be processed at a later time (such as is done in App-V)?

 

2) When upgrading an MSIX package, what is the difference between the switches:

    -ForceApplicationShutdown 

    -ForceTargetApplicationShutdown

In particular, are there situations where one might fail and the other succeed?  I'm guessing that if you specify only the target application it is possible the Add might not be able to complete successfully in some cases.

 

 

1 Reply

 


@TIMOTHY MANGAN wrote:

1) If an application is in use when an upgrade is attempted, will the Add-AppXPackage complete or fail?  If so is there any thought of adding the command to a pending queue to be processed at a later time (such as is done in App-V)?

[JV] The api surface allows a deferred registration of the package, so it updates on the next launch.  We working to expose that to the PowerShell cmdlets and the CSP that management tools use.

 

2) When upgrading an MSIX package, what is the difference between the switches:

    -ForceApplicationShutdown 

    -ForceTargetApplicationShutdown

In particular, are there situations where one might fail and the other succeed?  I'm guessing that if you specify only the target application it is possible the Add might not be able to complete successfully in some cases.

[JV] The difference is around framework packages and how we handle the shutdown of the related frameworks. For the most part you should rely on ForceTargetApplicationShutdown.

 


@TIMOTHY MANGAN