Hi there!
This is about uninstall methods of deployment software for a VB6 application which will be replacing the old Wise suite. Wise was very good although it didn't tick every single box, and despairing if there is anything cost effective enough to match it these days.
Here's a list of some (the obvious top_of_the-liners are way over budget):
From the other thread:
Some more recent
Now these may or may not suit everyone's requirements, but the majority of them should. However the big issue for me is myapp related stuff that gets put on the disk after the installation. Specifically myapp related config files and shortcuts.
Here's my own particular issue in regards to a scenario in un-installation:
The user may wish to create extra myapp related files in appdir. Fine, but they will remain on the disk after uninstall. The user may wish to retain some or all of these files/directories for whatever purpose. The same with myapp shortcuts. Easy enough to create a startmenu directory with the app link, but what about other created shortcuts to user files related to myapp? The uninstaller will want to deal with them in the same way.
Edit: Ideally the installer will have a facility to allow myapp to log all user file/directory creations (or deletions) to a section in its uninstall dat file.
However, any file/directory movements in the myapp directory (or shortcut directory) made outside of the myapp GUI might want to be handled differently in the uninstall process.
Inno Setup appears to have the means of addressing this, but there are issues. The code in this thread was very kindly added some years ago, but the Pascal code doesn't compile well at all in the recent release of Inno -it's just the spaces between operator/operand inserted by the BBCode. Plus it does not present a GUI to the user with checks for retention of all the extra files & directories.
Furthermore, Inno is not well received (also here) these days by some of vbforum's veteran posters.
Any suggestions as to what is the best way forward much appreciated. :)
Thanks for reading.
This is about uninstall methods of deployment software for a VB6 application which will be replacing the old Wise suite. Wise was very good although it didn't tick every single box, and despairing if there is anything cost effective enough to match it these days.
Here's a list of some (the obvious top_of_the-liners are way over budget):
From the other thread:
Some more recent
- Actual Installer
- Install Mate
- InstallForge
- Smart Install
- Install Creator (no price on the commercial version)
- Visual installer
Now these may or may not suit everyone's requirements, but the majority of them should. However the big issue for me is myapp related stuff that gets put on the disk after the installation. Specifically myapp related config files and shortcuts.
Here's my own particular issue in regards to a scenario in un-installation:
The user may wish to create extra myapp related files in appdir. Fine, but they will remain on the disk after uninstall. The user may wish to retain some or all of these files/directories for whatever purpose. The same with myapp shortcuts. Easy enough to create a startmenu directory with the app link, but what about other created shortcuts to user files related to myapp? The uninstaller will want to deal with them in the same way.
Edit: Ideally the installer will have a facility to allow myapp to log all user file/directory creations (or deletions) to a section in its uninstall dat file.
However, any file/directory movements in the myapp directory (or shortcut directory) made outside of the myapp GUI might want to be handled differently in the uninstall process.
Inno Setup appears to have the means of addressing this, but there are issues. The code in this thread was very kindly added some years ago, but the Pascal code doesn't compile well at all in the recent release of Inno -it's just the spaces between operator/operand inserted by the BBCode. Plus it does not present a GUI to the user with checks for retention of all the extra files & directories.
Furthermore, Inno is not well received (also here) these days by some of vbforum's veteran posters.
Any suggestions as to what is the best way forward much appreciated. :)
Thanks for reading.