I'm trying to create a custom command line parameter so that the user could optionally omit certain actions from the installer.
e.g., I'd like to be able to do this:
setup /omit_dotnet
which would cause the included dotnet installer to NOT be run (which happens to be a requirement for some customer environments).
It is simple enough to do this with the following format:
setup /omit_dotnet=true
but I would prefer to get rid of the =true portion. The problem is that it does not seem possible to distinguish between a command line param which has no value specified vs. the parameter not existing at all.
On https://jrsoftware.org/ishelp/index.php?topic=consts it says the following:
{param:ParamName|DefaultValue}
Embeds a command line parameter value.
ParamNamespecifies the name of the command line parameter to read from.DefaultValuedetermines the string to embed if the specified command line parameter does not exist, or its value could not be determined.
Is there any way to tell the difference between the "does not exist" and the "value could not be determined" cases?
There might be another way to accomplish the overall goal - I did look into using tasks or components; but we currently have none of those defined because the installer GUI is deliberately very simple.
