Use Microsoft Windows Installer and get both for free. Indeed, I wouldn't
develop a custom installation routine unless there's a very good reason to
do so. While Windows Installer is capable of doing almost anything a decent
installation routine needs, and is extensible with custom actions, I'd even
say there is no reason to bother with custom installation routines at all -
well, unless Windows Installer cannot be used for some reason.
If you used a Setup project, or created an .MSI (the build output for a
setup project), you can write a batch file that will uninstall it if you
know the ProductCode (which is a property of the setup project).
The batch file would say:
msiexec /x {productcode}
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.