This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Shortcut suspicions
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 03, 2010
04:26 PM
Shortcut suspicions
The scenario below refers to an individual executable file that is updated. The name of the executable does not change, only the size and build time.
When creating a major update, if I delete the contents of the Program Assistant->Application Files->Add Files panel and then add an updated executable (using the Add File button) then two shortcuts to the same executable appear within the Program Assistant->Shortcuts panel.
If I just update the executable by overwriting it within the directory that the Program Assistant->Application Files->Add Files panel is statically linked to, then all is fine.
Now that I have discovered this quirk, I can work around it but the next guy to update the Program Assistant->Application Files->Add Files panel may not notice this until the test team discovers a bad shortcut.
What is the best practice here? I don't want to use dynamic linking due to the warnings in the help files and forums regarding it's use with executable files.
When creating a major update, if I delete the contents of the Program Assistant->Application Files->Add Files panel and then add an updated executable (using the Add File button) then two shortcuts to the same executable appear within the Program Assistant->Shortcuts panel.
If I just update the executable by overwriting it within the directory that the Program Assistant->Application Files->Add Files panel is statically linked to, then all is fine.
Now that I have discovered this quirk, I can work around it but the next guy to update the Program Assistant->Application Files->Add Files panel may not notice this until the test team discovers a bad shortcut.
What is the best practice here? I don't want to use dynamic linking due to the warnings in the help files and forums regarding it's use with executable files.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 07, 2010
09:40 AM
As long as the target file name and location aren't changing, leaving the shortcut alone and just replacing the file seems it would do the trick.