How does winget choose an MSI over an EXI when the manifest has both?

[mjr4077au]

Take https://github.com/microsoft/winget-pkgs/blob/master/manifests/m/Mozilla/Firefox/115.0.2/Mozilla.Firefox.installer.yaml for example, this manifest offers both MSI and EXE install types for my language and architecture and I was wondering how the MSI is chosen over the EXE?

Example PowerShell code.

PS C:\Users\User\Desktop> Invoke-RestMethod -UseBasicParsing -Uri https://raw.githubusercontent.com/microsoft/winget-pkgs/master/manifests/m/Mozilla/Firefox/115.0.2/Mozilla.Firefox.installer.yaml | ConvertFrom-Yaml | Select-Object -ExpandProperty Installers | Where-Object {$_.InstallerLocale -eq [System.Globalization.CultureInfo]::CurrentUICulture.Name -and $_.Architecture.Equals('x64')}


InstallerLocale        : en-GB
Architecture           : x64
InstallerType          : wix
Scope                  : machine
InstallerUrl           : https://download-installer.cdn.mozilla.net/pub/firefox/releases/115.0.2/win64/en-GB/Firefox%20Setup%20115.0.2.msi
InstallerSha256        : C04620671E0D5450193F1815172BB0B5337E0DC0DFBF19B85BA58D84385D091F
ProductCode            : {1294A4C5-9977-480F-9497-C0EA1E630130}
AppsAndFeaturesEntries : {@{DisplayName=Mozilla Firefox (x64 en-GB); ProductCode=Mozilla Firefox 115.0.2 (x64 en-GB)}}

InstallerLocale        : en-GB
Architecture           : x64
InstallerType          : exe
Scope                  : machine
InstallerUrl           : https://download-installer.cdn.mozilla.net/pub/firefox/releases/115.0.2/win64/en-GB/Firefox%20Setup%20115.0.2.exe
InstallerSha256        : FBA16C83B68A2EE254564A8879B3737E220A5C28AE3C98E6F3176F3E2DBDE879
InstallerSwitches      : @{Silent=/S; SilentWithProgress=/S}
AppsAndFeaturesEntries : {@{DisplayName=Mozilla Firefox (x64 en-GB); ProductCode=Mozilla Firefox 115.0.2 (x64 en-GB)}}

From the source, it appears it purely comes down to the order of the branching in AppInstaller::Manifest::ConvertToInstallerTypeEnum() but I'm not 100% sure it's as simple as that?

winget-cli/src/AppInstallerCommonCore/Manifest/ManifestCommon.cpp

Lines 120 to 167 in 881904c

	InstallerTypeEnum ConvertToInstallerTypeEnum(const std::string& in)
	{
	std::string inStrLower = Utility::ToLower(in);
	InstallerTypeEnum result = InstallerTypeEnum::Unknown;
	if (inStrLower == "inno")
	{
	result = InstallerTypeEnum::Inno;
	}
	else if (inStrLower == "wix")
	{
	result = InstallerTypeEnum::Wix;
	}
	else if (inStrLower == "msi")
	{
	result = InstallerTypeEnum::Msi;
	}
	else if (inStrLower == "nullsoft")
	{
	result = InstallerTypeEnum::Nullsoft;
	}
	else if (inStrLower == "zip")
	{
	result = InstallerTypeEnum::Zip;
	}
	else if (inStrLower == "appx" || inStrLower == "msix")
	{
	result = InstallerTypeEnum::Msix;
	}
	else if (inStrLower == "exe")
	{
	result = InstallerTypeEnum::Exe;
	}
	else if (inStrLower == "burn")
	{
	result = InstallerTypeEnum::Burn;
	}
	else if (inStrLower == "msstore")
	{
	result = InstallerTypeEnum::MSStore;
	}
	else if (inStrLower == "portable")
	{
	result = InstallerTypeEnum::Portable;
	}
	return result;
	}

[denelon]

The client now has a "--installer-type" argument that can be used to specify the installer type preferred.

[mjr4077au]

Just regarding this, are the accepted values documented? When something incorrect is used, it throws an error but doesn't tell you correct values. I'm assuming the string literals in the source like wix, inno, etc are what's accepted?