-
Notifications
You must be signed in to change notification settings - Fork 693
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
[.NET 9 UWP] UWP App with Packaging Project template generates MSIX that does not run #10059
Comments
Is this specific to using WAP? That is, does the same app work correctly with single-project? Could you share a minimal repro? |
Single-project works fine, in both F5 and the resulting package. Minimal repro can be created straight from the template, but here it is: WAPApp.zip |
Mh, I think this is a known issue where the "PublisherDisplayName" property in the manifest isn't replaced correctly. It's on my todo to fix that, just haven't had time to do that just yet. As a workaround, can you try updating that manually in the manifest file, and see if once you do that the issue goes away? IIRC last time I tried doing that and after that the app would just work correctly. |
Doesn't look like it, I changed Output under the debugger:
|
Mmh I can repro. To be clear, here's what I'm seeing (for the WAP project):
Add-AppxPackage -Path "C:\Users\sergiopedri\source\repos\App9\AppWithWap1\AppWithWap1.Package\AppPackages\AppWithWap1.Package_0.0.2.0_x64_Debug_Test\AppWithWap1.Package_0.0.2.0_x64_Debug\AppxManifest.xml" -Register On the extracted .msix file. I wonder if perhaps it's not installing some framework dependencies it needs. I'll take a look. |
It seems that resource.pri does not include the necessary resources. |
I have a fix for this (we weren't wiring up MRT Core in this scenario), I'll share details when it's publicly available. |
Describe the bug
UWP App with Packaging Project template generates MSIX that does not run.
F5 in VS works though, when the startup project is set as the Packaging project.
Steps to reproduce the bug
Expected behavior
The app starts up as expected.
Screenshots
No response
NuGet package version
None
Windows version
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: