Honor MSI parameters for scripted installations #133
Labels
Milestone
Comments
|
CC @astrojonathan, @philrosenfield for the planned Windows release. |
pkgw
added a commit
to pkgw/wwt-windows-client
that referenced
this issue
Jan 5, 2022
Following up (finally) issue WorldWideTelescope#133. I'll write up a summary there. Basically there is no good way to get a sensible user experience becaue (1) checkboxes only work with properties being defined or undefined and (2) the Visual Studio installer generation has a bug that prevents checkbox properties from being controlled from the command line. Subsequent commits will address the second issue.
Merged
|
It's taken a while but I think I have a fix for this issue! It ended up being a real mess -- gritty details in #194. The candidate fix should make it into the next beta release, which I want to put out soon so that I can test the auto-updating functionality more generally. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The MSI installer seems to use the parameter
AUTOUPDATEto determine if autoupdates should be enabled, but passingAUTOUPDATE=0as a parameter to the installer gets ignored andAUTOUPDATEis changed from 0 -> 1 during the install. It would be nice if theAUTOUPDATE=0value passed on the command line at install time would be honored by the installer.Similarly for the legacy installer both
AUTOUPDATE=0andLAUNCHEXCELADDIN=0are not honored from the command line.The text was updated successfully, but these errors were encountered: