[New feature]: Allowing the package author to specify the recommended/default installer type

[DuckDuckStudio]

One of my packages (DuckStudio.GitHubView) can be installed via Inno, portable or zip in WinGet. I don't recommend using the zip installation as it requires additional dependency (.NET Runtime), but WinGet seems to default to the zip installation...

I hope I can enable users to use the zip installation only when necessary, instead of defaulting to it.

In the manifest, I hope the priority of certain installer can be increased or decreased through "Recommended Installer Type" or other methods (or the default installer type can be specified).

[Trenly]

• Related to Ability to specify a default installer type in the manifest winget-cli#3866

@denelon - This should be moved to CLI

[Trenly]

@DuckDuckStudio - As a temporary workaround, move the Zip installers to the bottom of the installer list. WinGet should take the first applicable installer in the list, if there are no other preference indicators

[DuckDuckStudio]

@DuckDuckStudio - As a temporary workaround, move the Zip installers to the bottom of the installer list. WinGet should take the first applicable installer in the list, if there are no other preference indicators

• Modify: DuckStudio.GitHubView version 1.0.4 (Auto) #255769

Is there any document on this now? If not, I think maybe can write a temporary document for this and link to related issues until the relevant feature is relevant(implemented?).

[Trenly]

Is there any document on this now? If not, I think maybe can write a temporary document for this and link to related issues until the relevant feature is relevant(implemented?).

It's mentioned in the issue I linked. I think a few PRs over at CLI discuss it.

Basically, there are sets of applicability filters that are generated based on the users winget settings, system information, and command line arguments. These filters can have different strictness levels such as "required", "preferred", or "prohibited".

The CLI iterates over each installer in order to see if it is an applicable installer (matches requirements and prohibitions). If it is applicable, it then checks to see if it is "better" than the currently selected installer based on the preferences. If better, it is set as the currently selected installer and comparisons continue, if equal or not better, the current installer is left as is. After all comparisons are done, the application is installed using the currently selected installer.

Additionally, there is supposed to be a default type preference built in, but I’m not sure that its working properly

• Ability to specify a default installer type in the manifest winget-cli#3866 (comment)
• WinGet installer type precedence? Chooses portable over MSI/WiX by default winget-cli#5248 (comment)