The update is applied immediately after AddPackageAsync.

[HppZ]

from doc:

The update will be applied the next time your app is shut down.

await packagemanager.AddPackageAsync(new Uri("https://trial3.azurewebsites.net/HRApp/HRApp.msix"), null, AddPackageOptions.ForceApplicationShutdown

same for UpdatePackageAsync.

but according to my test, the update is applied immediately after AddPackageAsync, and the app is killed by Windows. why?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 61dbc475-482a-3e2f-b41e-bb9d35d100e5
• Version Independent ID: 93e1b53d-8150-5693-ca85-acb317f1f666
• Content: Update non-Store published apps from your code - MSIX
• Content Source: msix-src/non-store-developer-updates.md
• Product: msix
• GitHub Login: @Huios
• Microsoft Alias: diahar

[HarshadaKshirsagar]

You could use DeferRegistrationWhenPackagesAreInUse. It is a Boolean value, TRUE indicates that registration of the main package or dependency packages will be delayed until the next time the application is activated if the packages are currently in use; otherwise, FALSE. We will update the doc to reflect this.

References: AddPackageOptions Class https://docs.microsoft.com/en-us/uwp/api/windows.management.deployment.addpackageoptions?view=winrt-22000

AddPackageOptions.DeferRegistrationWhenPackagesAreInUse Property https://docs.microsoft.com/en-us/uwp/api/windows.management.deployment.addpackageoptions.deferregistrationwhenpackagesareinuse?view=winrt-22000#windows-management-deployment-addpackageoptions-deferregistrationwhenpackagesareinuse

[HppZ]

and what is the difference between AddPackage* and UpdatePackage*？

[HarshadaKshirsagar]

Either can be used for updating, we recommend you use AddPackage for install and update both. It simplifies code.

[HppZ]

thanks