Skip to content

after _Configure a WinUI 3 project for AppContainer_ can’t deploy #456

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dogfuntom opened this issue Apr 29, 2025 · 1 comment
Open

Comments

@dogfuntom
Copy link

dogfuntom commented Apr 29, 2025

What I did:

  1. the packaged option in https://github.com/MicrosoftDocs/windows-dev-docs/blob/4b6b0b9db41befdc200c800c5fe01b0c43ce2494/hub/apps/winui/winui3/create-your-first-winui3-app.md
  2. the last sub-option in single-project option in https://github.com/MicrosoftDocs/msix-docs/blob/1ce4da9433842a8c5e47453a3191f47e0fde7297/msix-src/msix-container.md

The result:

  • error DEP0700 [0x80080204]
  • in bin\x64\Debug\net8.0-windows10.0.19041.0\win-x64\AppxManifest.xml there’s <Application Id="App" Executable="MsixContainerIssue.exe" EntryPoint="Windows.FullTrustApplication" uap10:TrustLevel="appContainer" uap10:RuntimeBehavior="packagedClassicApp">

Sample project: https://github.com/dogfuntom/MsixContainerIssue/commits/main/

conclusion

The article implies that EntryPoint="$targetentrypoint$" will be built into EntryPoint="Windows.PartialTrustApplication" auto-magically after adding uap10⁠-⁠related attributes – but it’s still EntryPoint="Windows.FullTrustApplication" regardless.

@dogfuntom
Copy link
Author

According to the table in App development framework feature comparison, Sandboxing (AppContainer) in Not supported in WinUI 3. Is it a contradiction?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant