Setting AppxPackageName breaks msixbundle generation

[marcelwgn]

Describe the bug

For our project, we have set the AppxPackageName. When generating an MSIX bundle using the "Create package" flow from VS, this resulted however in no proper MSIX bundle being generated, it only contained the latest arch.

When this property was removed, the MSIX bundle works correctly and contains multiple packages.

Steps to reproduce the bug

1. Set AppxPackageName for csproj
2. Create msix bundle with multiple platforms using the VS "Create package" flow

Expected behavior

No response

Screenshots

No response

NuGet package version

2.0.1

Packaging type

Packaged (MSIX)

Windows version

No response

IDE

No response

Additional context

No response

[dongle-the-gadget]

I suppose if you only need the bundle name to be changed, you can use AppxBundleNameForOutput instead?

[guimafelipe]

I suppose if you only need the bundle name to be changed, you can use AppxBundleNameForOutput instead?

The problem here is not the bundle name, but the name of the MSIX files that go into the bundle. If the user sets AppxPackageName in the project file, all the MSIX's in the bundle would have the same name (instead of the name with the prefix of the platform they are built for) and then they will overwrite each other.