microsoft / microsoft/winget-cli

Add way to specify MSIX details such as Package Family Name for AppsAndFeatures Entries

Open
#2,804 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Manifest Issue-Feature
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

Description of the new feature / enhancement

I ran into an oddity with the Microsoft Windows App SDK Runtime where the exe installer is just a wrapper for several MSIX packages. It would be nice if the details of the MSIX package, such as the PackageFamilyName, could be specified in the apps and features entries

https://github.com/Trenly/winget-pkgs/blob/9cf38f7be8b2f18cab84cefed19b00d957c5e9db/manifests/m/Microsoft/WindowsAppRuntime/1/2/1.2.2/Microsoft.WindowsAppRuntime.1.2.installer.yaml#L12-L15

PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs> Get-AppxPackage |?{$_.name -match 'microsoft' -and $_.name -match 'runtime'}|Select-Object -Property Name,Version,Architecture,PackageFamilyName

Name                                            Version         Architecture PackageFamilyName
----                                            -------         ------------ -----------------
Microsoft.WindowsAppRuntime.1.2                 2000.707.2303.0          X64 Microsoft.WindowsAppRuntime.1.2_8wekyb3d8bbwe
Microsoft.WindowsAppRuntime.1.2                 2000.707.2303.0          X86 Microsoft.WindowsAppRuntime.1.2_8wekyb3d8bbwe
MicrosoftCorporationII.WinAppRuntime.Main.1.2   2000.707.2303.0          X64 MicrosoftCorporationII.WinAppRuntime.Main.1.2_8wekyb3d8bbwe
MicrosoftCorporationII.WinAppRuntime.Singleton  2000.707.2303.0          X64 MicrosoftCorporationII.WinAppRuntime.Singleton_8wekyb3d8bbwe
Microsoft.WinAppRuntime.DDLM.2000.707.2303.0-x6 2000.707.2303.0          X64 Microsoft.WinAppRuntime.DDLM.2000.707.2303.0-x6_8wekyb3d8bbwe
Microsoft.WinAppRuntime.DDLM.2000.707.2303.0-x8 2000.707.2303.0          X86 Microsoft.WinAppRuntime.DDLM.2000.707.2303.0-x8_8wekyb3d8bbwe
Proposed technical implementation details

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked winget-pkgs manifest and the Apps and Features entry handling in winget-cli. Define how MSIX details such as PackageFamilyName should be specified and surfaced for wrapper installers, then verify the behavior with Windows App SDK Runtime packages.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.