WindowsAppSDK: Single-project MSIX doesn't support producing a MSIX Bundle
Describe the bug
Despite selecting “Generate app bundle = Always” in the UI, a .msixbundle file is not generated. The root cause is that single-project MSIX doesn’t support generating MSIX Bundles today, however that manifests as a bug to the developer since the UI allows you to select an option that doesn’t work.
Steps to reproduce the bug
- Create a new app
- Use the Package & Publish UI to start creating a package
- Select “Generate app bundle = Always” and select two build combinations
- Attempt to build the package
- Notice a silent error occurs
Microsoft.Build.Msix.Packaging.targets(341,5): error MSB6011: Invalid parameters passed to the Microsoft.Build.Msix.Symbols.WinAppSdkCheckFastlinkPdb task.
- Notice that no bundle is created, only separate MSIX’s
Expected behavior
A bundle should be created.
Screenshots
No response
NuGet package version
1.0.0
Packaging type
Packaged (MSIX)
Windows version
No response
IDE
Visual Studio 2022-preview
Additional context
No response
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 19
- Comments: 28 (2 by maintainers)
Any progress on this issue?
Unfortunately support for this won’t be part of the 1.2 release.
This is a major issue that has been open for almost 6 months without resolution (blocking me from releasing now). Microsoft, can you give an update here on when we can expect closure? What the actual issue is?
Been hacking away at this and I think I got something that will make this all work wonderfully:
https://gist.github.com/mattleibow/8332ed79b569c9d7bbdae64a6e8142a6
What is the status of issue?
Kind of mind-boggling there is just zero progress on this issue. Microsoft doesn’t want us to publish apps apparently. Even the milestone hasn’t been updated and still stands at “1.1”
Manual workaround for those in need:
“C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64\MakeAppx.exe” bundle /d “C:.…\Parent\Package” /p “C:.…\Parent\AppName_Bundle.msixbundle”
Theoretically someone should be able to create a post build script (and integrate it with VS project), but no success here so far.
Can we get some transparency here? We need to be able to plan. This clearly missed the 1.1 milestone (and then some). So, what is the new target?
Hi @JanRajnoha, thanks for the ping. I checked with the team on this and it looks like it’s something we have on our radar but with no concrete details to share right now. I did go ahead and at least clear the old milestone off, though.
I started using in my Azure DevOps pipelines something similar -> VS Build task for creating msix, call PowerShell for bundling (move msix to temp folder, call MakeAppx.exe) and that’s working without problems.