Articulate Studio 09 Desktip Shortcuts and setup.iss
I am following the instructions for a silent install of Articulate Studio 09 which is to record an iss file and use to manage the install but I am having a problem with the desktop shortcuts. http://www.articulate.com/support/kb_article.php?product=ap9&id=c26b33it7r8p The standard InstallShield setup.exe stuff...
The setup.exe extract 2 msi's both named Articulate Studio '09 Pro.msi but neither put shortcuts on the desktop. Are there any options I can use with the setup.exe or in the iss file to hide the desktop shortcuts?
Answers (3)
Turns out the EXE and the 2 MSI's all put GUIDs in the registry so I guess the MSI's do something, but I can't figure out what or how to manipulate them with an MST or through the EXE command line. So I gave up and made a secondary MSI that managed the required changes and included it with a CMD to handle the install. A setup.iss and uninstall.iss are required and one of the MSI's doesn't uninstall using the setup.exe so you need to uninstall it separately.
>The setup.exe extract 2 msi's both named Articulate Studio '09 Pro.msi
Why not simply create a transform for one of them and add the required shortcut(s) to it?
Comments:
-
Normally I would just remove the shortcut creation from the MSI's with an MST, but they are not what is creating the shrotcuts. I am not sure how I could create a transform to do this?
Also, I am not sure if/when the MSI's are run whether its before/during/after the shortcuts are created. - jmaclaurin 12 years ago
if you try using 'msiexec /a "c:\source folder\AS09.msi" targetdir="c:\1\"', that should create an admin version of the software. If you then check that for the shortcuts or create a transform file on that msi.
Comments:
-
Huh, I don't know what to say other than I don't think you read the entire question or the following responses. - jmaclaurin 12 years ago
Turns out the EXE and the 2 MSI's all put GUIDs in the registry so I guess the MSI's do something, but I can't figure out what or how to manipulate them with an MST or through the EXE command line. So I gave up and made a secondary MSI that managed the required changes and included it with a CMD to handle the install.
A setup.iss and uninstall.iss are required and one of the MSI's doesn't uninstall using the setup.exe so you need to uninstall it separately.