Microsoft.WindowsAppSDK.Runtime's MSIX.inventory file has wrong DDLM PackageFullName

[azchohfi]

Describe the bug

The MSIX.inventory file has a list of MSIX files and their corresponding PackageFullName, for each architecture.
For example, for Nuget Microsoft.WindowsAppSDK.Runtime version 1.8.251106002, that file contains:

Microsoft.WindowsAppRuntime.1.8.msix=Microsoft.WindowsAppRuntime.1.8_8000.675.1142.0_arm64__8wekyb3d8bbwe
Microsoft.WindowsAppRuntime.DDLM.1.8.msix=Microsoft.WindowsAppRuntime.DDLM.1.8_8000.675.1142.0_arm64__8wekyb3d8bbwe
Microsoft.WindowsAppRuntime.Main.1.8.msix=MicrosoftCorporationII.WinAppRuntime.Main.1.8_8000.675.1142.0_arm64__8wekyb3d8bbwe
Microsoft.WindowsAppRuntime.Singleton.1.8.msix=MicrosoftCorporationII.WinAppRuntime.Singleton_8000.675.1142.0_arm64__8wekyb3d8bbwe

If you want to know if this runtime (for this arch) is installed, you can use this file to check if each PackageFullName is installed. Still, this works only for 3 of these 4 packages.

For this particular version, the DDLM PackageFullName is **Microsoft.WinAppRuntime.DDLM**.8000.675.1142.0-a6_8000.675.1142.0_arm64__8wekyb3d8bbwe. Not sure if only the Microsoft.WindowsAppRuntime.DDLM prefix should be changed to Microsoft.WinAppRuntime.DDLM, but there is clearly a mismatch.

Steps to reproduce the bug

1. Download Nuget Microsoft.WindowsAppSDK.Runtime version 1.8.251106002.
2. Manually install all files from Microsoft.WindowsAppSDK.Runtime.1.8.251106002\tools\MSIX\win10-arm64 (in my case, for arm64).
3. Open MSIX.inventory file.

Expected behavior

For each string after the = sign, there should be a matching package full name, or at least a newer version installed.

Screenshots

No response

NuGet package version

Windows App SDK 1.8.4: 1.8.260101001

Packaging type

No response

Windows version

No response

IDE

No response

Additional context

No response

[ssparach]

Thank you for your feedback. The DDLM package has a package full name in the format Microsoft.WinAppRuntime.DDLM.- and the prefix does need to be changed here to fix this issue.