jantari
jantari
@denelon **The licensed/paid version of FortiClient** is an MSI installer that requires an MST transforms file in order to be installed (silently or non-silently) in order to connect to the...
I just tried deploying a licensed FortiClient (MSI + MST) using the following manifest (excerpt): ```yaml InstallerType: zip NestedInstallerType: wix Scope: machine NestedInstallerFiles: - RelativeFilePath: FortiClient.msi InstallerSwitches: Custom: TRANSFORMS=FortiClient.mst REBOOT=ReallySuppress...
But InstallerType portable is not the same as InstallerType zip: https://github.com/microsoft/winget-cli/blob/2fece93b79e3c844af3bb096bf0f5ed31389379e/schemas/JSON/manifests/v1.7.0/manifest.installer.1.7.0.json#L55-L69 Unless I'm misunderstanding, the behavior and handling of portable packages should not apply to ZIP + NestedInstaller packages.
Any new developments or comments on this?
[42](https://www.youtube.com/watch?v=5ZLtcTZP2js)
Originally reported by @mklement0 in https://github.com/PowerShell/PowerShell/issues/8751 > This issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version...
Any bug can be considered "design" because it's always technically coded to behave that way. But if it makes no sense, goes against expectations, there's no good reason for the...
@mklement0 you have contributed many fantastic issues and discussions to PowerShell, but I don't think it's necessary to convince @237dmitry of your opinion here, what matters is that we can...
*activity* Yes this is obviously still an issue.