Tweet
Command-Line Arguments?
Hi,
I use AutoPlay Studio to create entries in the Registry. It serves as a "front end" to Setup Factory. This is because SF has only 4 install types, but I need 11. SF then looks at the registry to determine whether to install each file.
Two problems:
1) If a user runs SETUP.exe directly, there is no way to control which files install (as I don't use install types at all). So, either no files install, or it will duplicate the last install.
2) One of my 11 installs does not copy any of my 600 files. It just sets up a shortcut. But, it still takes 20 seconds or so to execute, and the "% complete" bar is empty the whole time (as it displays every single file name).
Maybe I need a separate SF install for my 2nd situation? But, it would be nice to have just one install program like I used to have.
As for the first problem, it would be really nice if SF could read in command-line arguments into variables. I wouldn't have to put my temporary data into the registry.
Also, I have been considering using Radio Buttons. However, the "default" radio button is "hard-coded". It would be nice to have this populated based on a variable.
But my ultimate wish would be to have more than 4 install types, and have the install type default to a variable from the command line, rather than being "hard-coded".
I would appreciate your thoughts.
TIA.
VictorReinhart
I use AutoPlay Studio to create entries in the Registry. It serves as a "front end" to Setup Factory. This is because SF has only 4 install types, but I need 11. SF then looks at the registry to determine whether to install each file.
Two problems:
1) If a user runs SETUP.exe directly, there is no way to control which files install (as I don't use install types at all). So, either no files install, or it will duplicate the last install.
2) One of my 11 installs does not copy any of my 600 files. It just sets up a shortcut. But, it still takes 20 seconds or so to execute, and the "% complete" bar is empty the whole time (as it displays every single file name).
Maybe I need a separate SF install for my 2nd situation? But, it would be nice to have just one install program like I used to have.
As for the first problem, it would be really nice if SF could read in command-line arguments into variables. I wouldn't have to put my temporary data into the registry.
Also, I have been considering using Radio Buttons. However, the "default" radio button is "hard-coded". It would be nice to have this populated based on a variable.
But my ultimate wish would be to have more than 4 install types, and have the install type default to a variable from the command line, rather than being "hard-coded".
I would appreciate your thoughts.
TIA.
VictorReinhart
Comment