12-09-2015 09:47 AM
___________________________________________________________________________________________________________
But you can include multiple executables in an installer! You'd need to be able to select which one to use.
(Or no executable at all - I sometimes create 'prerequisites' installers to install the RTE/drivers that don't even include an executable)
___________________________________________________________________________________________________________
That makes sense. I've kept my LabView projects pretty simplistic, with only one exe, so selectivity would be nice, but with only one exe it should default to that exe's icon. Or possiblye the icon selected could default to the top included exe in the installer list?? With the idea of selectivity if a person wanted they could then choose a different icon if they wish.
10-21-2022 02:38 PM
Those who deploy software should familiarize themselves enough with the windows registry to be confident doing simple things like this. This works, but you have to enter the explicit path, unless someone knows how to grab the [TARGETDIR] property as well?
These settings are all in the installer properties dialog.
First put the icon file in a nice place, like here with your application.
Then tell windows uninstall the path
By default the property [ProductCode] is a random key and unique for each build of the installer, even if you keep the upgrade code constant. (another interesting subject) Therefore you should have no worries about affecting some registry entry that is already in place.