search

wixtoolset / issues

WiX Toolset Issues Tracker
http://wixtoolset.org/
129 stars 36 forks source link

Prerequisites (other than .NET) from winget using id and version #7262

Open Wallby opened 1 year ago

Wallby commented 1 year ago

Feature requests

Bundling an installer increases the size of the installer and doesn't support updates. Specifying a download URL can break every installer if that URL changes. Thus an option to specify only a download winget ID without having to bundle an installer file nor specify a download URL. The download URL can be deduced from the winget package (see comment below).

barnson commented 1 year ago

It's not clear what you're looking for. My guess is that you want Burn to be able to treat WinGet as a download source. But it's not clear how that fits in with your listed examples. Please clarify and we can re-triage.

Wallby commented 1 year ago

It's not clear what you're looking for. My guess is that you want Burn to be able to treat WinGet as a download source. But it's not clear how that fits in with your listed examples. Please clarify and we can re-triage.

I think might be unclear due to my lack of understanding of how different versions of programs are handled in windows. .NET uses a program per version right? Thus multiple versions would, unlike as it is in linux, be entirely up to the implementation support or not? From my experience as a user of programs on windows it seems that the common approach is if a version of an installed program is not supported for the program to present an error and stop the program?

A winget package contains an "InstallerUrl" (example) thus, if I understand how this works in wix correctly, instead of specifying a "DownloadURL=" for MsiPackage/ExePackage (as done here) there would be a "DownloadWingetID=" or something instead?

Advantage would be that if a developer changes to a different host they can change the URL in winget without breaking the current distributed installers?

Also a note from the microsoft/winget-pkgs repository about which types of installers are supported..

Note: At this time installers must be MSIX, MSI, APPX, or .exe application installers. Script-based installers and fonts are not currently supported.

Wallby commented 1 year ago

I editted the issue description.

Wallby commented 1 year ago

On the winget side there's apparently work on this as well, not sure if would be relevant.. https://github.com/microsoft/winget-cli/issues/163