creating a condition on the desktop shortuct and program menus in setup programs
-
Hello, Does anyone know if there is any way to add a condition to your setup project so that the user can choose if they want a desktop shortcut or a program menu by selecting a checkbox. I know that you can use conditions on files, but I can't get it to work with shortcuts. I tried to apply the condition to the folders instead of the shortcuts themselves, but the setup program doesn't seem to care. It just ignores if the checkboxes are checked or unchecked. Is there another way to do this? I don't want to force desktop shortcuts or program menu groups upon the user. Thanks, Blake
-
Hello, Does anyone know if there is any way to add a condition to your setup project so that the user can choose if they want a desktop shortcut or a program menu by selecting a checkbox. I know that you can use conditions on files, but I can't get it to work with shortcuts. I tried to apply the condition to the folders instead of the shortcuts themselves, but the setup program doesn't seem to care. It just ignores if the checkboxes are checked or unchecked. Is there another way to do this? I don't want to force desktop shortcuts or program menu groups upon the user. Thanks, Blake
Not with VS.NET's Windows Installer project designer. It provides very little exposure for the tables that make up an installer database. Typically - in a real Windows Installer editor (Wise, InstallShield, Microsoft's Orca, etc.) - the shortcut should be associated with the component that contains the executable (which should be the key file). In some cases, developers put the shortcut in a different component and add a condition to it. If your app only installs a couple shortcuts and you want one option that determines if they are installed or not, you can have a dialog control (checkbox, for example) that sets a property that is used in the InstallExecuteSequence table for the Condition field. In either case, though, VS.NET won't let you do it. You can download the Windows Installer SDK (part of the Platform SDK) from MSDN and use the Orca utility (the MSI is downloaded, but you have to install it manually for some strange reason) to edit the tables manually after the MSI is compiled.
-----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----