Description of the new feature / enhancement

For new installs where several install types/ extensions are available, I'd like the ability to specify it with winget install.

Examples packages with both EXE and MSI available:

• 7-Zip
  • Because Igor prefers and recommends EXE over MSI.
    • https://sourceforge.net/p/sevenzip/support-requests/289/
• KeePass
  • Because Winget does not work with --location on this specific package
    • -l,--location option not working on all msi packages #1857.
  • Important because EXE and MSI installs to different locations, potentially four different locations historically, thus specifying install location makes making detection rules easier.

This should of course be combined with the ability to:

• Specify architecture with winget install, which is already supported:
  • https://docs.microsoft.com/en-us/windows/package-manager/winget/install
• Specify preferred installer type/ extension inside the settings file -> Install behavior, which is currently not supported.
  • https://github.com/microsoft/winget-cli/blob/master/doc/Settings.md#install-behavior

Proposed technical implementation details

I don't know. This get's messy quick. Manifest already has installertype, but that hints towards installer vendor (Inno, Nullsoft etc.) rather than MSI vs. EXE.

installertype should be used to store the general installer type IMO, like:

• EXE
• MSI
• MSIX
• ZIP\EXE
• ZIP\MSI
• ZIP\MSIX

While installervendor could store the vendor/ creator of the installer, like:

• Inno
• Microsoft (MSI, MSIX)
• Nullsoft