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
- :
- DOS Shortcut Not Deleted On Uninstall
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
‎Oct 14, 2009
05:46 PM
DOS Shortcut Not Deleted On Uninstall
I have a really simple installation. It creates two shortcuts. One is a shortcut to a .NET assembly. The other is a shortcut to a DOS program.
On uninstall, the .NET assembly shortcut is removed, but not the DOS program shortcut.
I have tried everything I can think of to delete this thing, but it will not go away. Neither on XP or Vista (both 32-bit).
I'm using InstallShield Professional 2010 and this is a Basic MSI project.
On uninstall, the .NET assembly shortcut is removed, but not the DOS program shortcut.
I have tried everything I can think of to delete this thing, but it will not go away. Neither on XP or Vista (both 32-bit).
I'm using InstallShield Professional 2010 and this is a Basic MSI project.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 16, 2009
03:10 PM
I found a way around this problem. What's interesting is that there are no errors in the uninstallation log. So, why it doesn't work, and why it doesn't show up in the log is something I can't explain.
What I did was just create a CA, called it in the User Interface sequence after ExecutionAction, with a condition of REMOVE="ALL". It's brute force, but it works.
What I did was just create a CA, called it in the User Interface sequence after ExecutionAction, with a condition of REMOVE="ALL". It's brute force, but it works.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 24, 2010
04:30 PM
I have this same problem with a simple install that creates two shortcuts to .exe files. How did you get around this? What type of Custom Action did you create?
