Proposal: Deploy WinUI 3 runtime using Framework Packages for Packaged and Unpackaged apps #2767
Labels
appModel-win32
Exclusive to WinUI 3 Win32 Desktop apps
area-ProjectSystem
feature proposal
New feature proposal
product-winui3
WinUI 3 issues
team-Markup
Issue for the Markup team
Summary
WinUI 3 runtime will be distributed as Framework Packaged for UWP and Packaged WinUI 3 Apps. However, Framework Packages don’t work for apps that are no using MSIX as the deployment mechanism. This proposal is for enabling unpackaged WinUI 3 apps can register WinUI 3 Framework Package dependency. This dependency should be downloaded and updated automatically without application code required, as packaged UWP apps do today.
Rationale
Deploy the WinUI runtime using the Framework Package mechanism, like UWP apps service updates. The Framework Packages are hosted on the Microsoft Store and automatically deployed to the app’s device when there is an update. This automatic update helps to ensure that the customers always have the latest available version of the library installed on their devices. The framework packages mechanism was designed for the MSIX deployment and requires the package manifiest to register these dependent packages (dependencies) and the packaged identity to allow them be deployed.
Below there is a sample of Framework Packages dependencies from a package manifest:
However, Framework Packages don’t work for apps that are no using MSIX as the deployment mechanism. And as a consequence, each unpackaged Desktop WinUI apps will need to carry on a copy of the runtime binaries and there is not servicing via Store (for updating critical bugs, for instance).
Unpackaged Desktop WinUI apps should be able to register Framework Package dependencies (e.g. using the SxS manifest) . Some subsystem should downloaded and updated these dependencies automatically without application code required.
Scope
The text was updated successfully, but these errors were encountered: