-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InstallShield InstallerType Support #1247
Comments
@OfficialEsco do you have a URL to any documentation so we can take a look? |
Ooops i meant InstallShield, not InstallShell 🤦♂️ I can't seem to find concrete documentation on it, i just know its a oooooold one, i often see it using --s/--silent switches, but it also seems to accept /s /silent. I have a feeling we have a few InstallShield's among the exe InstallerTypes because it can also automatically install on exe launch and then it automatically opens the application. Example which is why i suggested it: microsoft/winget-pkgs#19464 @palenshus probably knows a little more, also requires support in wingetcreate, but for now it could add the --silent switch |
@OfficialEsco, if we can detect it, and we have a way to reason about the version used to validate switches this would be a great addition. It looks like the current version of Install Shield can produce MSIX, and earlier than that MSI. We will have to see how reliable it is from a detection and switch handling perspective. |
InstallShield has been around for 30 years. I don't know how relevant 16-bit and Win95 era installers are today but somebody should perhaps do some research before sprinkling There are some open source IS decompressors out there, they probably know how to detect different IS versions... |
Well, https://github.com/microsoft/winget-pkgs/search?p=1&q=%22--silent%22&type=code this is a start on exe's which accept |
InstallShield document about command-line parameters: |
Description of the new feature/enhancement
Why is there no InstallShield InstallerType?
microsoft/winget-pkgs#1161
Proposed technical implementation details (optional)
The text was updated successfully, but these errors were encountered: