Printable View
let's say you want to have 1 installer that installs the vb runtimes you need, and then a seperate installer(s) for your other program(s)
now, we all know that the run times won't do anything by themselves, so there's no harm in just leaving them on the person's computer. also, having an add/remove might be annoying to some. but there's others that want everything to have an add/remove... i dunno
Make things simple: If you install something, make sure there's a way to remove it.
oh yeah....... i guess the installer would use merge modules..... so even if you used the uninstall, the files wouldn't be removed :p
Just have it set up like other installers...
somefile.ext may still be used by other applications, do you want to remove it?
But really, VB6 runtimes aren't specific to only your program, so they shouldn't be removed(even if your program had to install them or update them).
If in doubt, install to your application's directory, and then remove them.