Complex installers

[denelon]

Description of the new feature/enhancement

As we get closer to supporting .zip and standalone .exe installers, we need some additional mechanisms to identify a few different scenarios. These include what kind of an installer is inside of .zip files. It also includes scenarios where a package is distributed with a .exe installer, but it also contains an .msi installer (PowerToys).

Proposed technical implementation details (optional)

We would add a new node to the Installers called "NestedInstallerType".

This example would help fix the upgrade scenario related to PowerToys:

Installers:
  - InstallerType: exe
    NestedInstallerType: msi
    InstallerArchitecture: x64
    InstallerSHA256: 12341234123412341234123412341234123412341234
    InstallerURL: https://www.contoso.com/awesomeapp/1.0.0/awesomeapp.x64.exe

This example is for a nullsoft installer distributed inside of a .zip file, but this could also be .exe, inno, wix, etc.

Installers:
  - InstallerType: zip
    NestedInstallerType: nullsoft
    InstallerArchitecture: x64
    InstallerSHA256: 12341234123412341234123412341234123412341234
    InstallerURL: https://www.contoso.com/awesomeapp/1.0.0/awesomeapp.x64.zip

This example is for a standalone / portable executable (these are not yet supported) inside of a .zip file.

Installers:
  - InstallerType: zip
    NestedInstallerType: standalone
    InstallerArchitecture: x64
    InstallerSHA256: 12341234123412341234123412341234123412341234
    InstallerURL: https://www.contoso.com/awesomeapp/1.0.0/awesomeapp.x64.zip

[denelon]

This was included in the Apps & Features section for multiple entries. We still have additional work in the client to support upgrade scenarios and matching logic for list.

winget-cli/schemas/JSON/manifests/v1.1.0/manifest.installer.1.1.0.json

Lines 412 to 415 in 5a97e26

	"InstallerType": {
	"$ref": "#/definitions/InstallerType"
	}
	},

#1396

[ffes]

Another example would be various Autodesk programs.

When you download "DWG TrueView" from https://www.autodesk.com/viewers (tab "Windows Viewer"), you will download an .exe. AFAICS this is a custom extractor that extracts all the required files in C:\Autodesk and starts the real setup.exe after it is extracted.

In the knowledge base of Autodesk is an example how to extract that sfx from the command line: https://knowledge.autodesk.com/search-result/caas/sfdcarticles/sfdcarticles/How-to-run-self-extraction-of-DWG-TrueView-2019-install-package-from-Command-Line.html