I use InstallShield for that and in that software you change the
product code and set up a new one and an upgrade setup with the
minimum and maximum version you plan to support as an upgrade
installation.
I'm not sure how you'd do that for an installer package created
directly using Windows Installer 1.1 or with Orca but there must be a
way. Try searching in the Orca or Windows Installer documentation on
MSDN to see what settings in Windows Installer you would have to set
and what GUID's you'd have to modify.
--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginners Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm
"Selgin" <(E-Mail Removed)> wrote in message
news:66618511-B9C6-4CEF-B066-(E-Mail Removed)...
> Hi all,
>
> I've created a VB6 COM Add-In (self-registering DLL file) for
Outlook 2000 and have used Windows Installer 1.1 to create a setup
(.msi) file to deploy it. It all works fine, but for one issue.
>
> If I update the DLL (and increase the version number) and build a
new .msi with the updated DLL, when I run the setup it doesn't
overwrite the existing DLL, thus not reflecting the updated DLL. The
setup asks me if I want to repair or remove the add-in, and if I
choose repair it doesn't update the DLL, just leaves the current
existing one.
>
> I would like it to overwrite the installed DLL without having to
uninstall and then install the updated add-in. Can anyone please
help?
>
> Thanks in advance,
> Selgin
>
>
>
>
>