Within the constraints of VS setups, custom actions and major upgrades
(RemovePreviousVersions) you can do something like this:
Have an uninstall custom action that saves those registry entries,
conditioned on UPGRADINGPRODUCTCODE which is set when you are being
uninstalled by a major upgrade.
Have an install custom action that looks for the saved registrry entries and
installs them.
--
Phil Wilson
[MVP Windows Installer]
[quoted text, click to view] "Paul Hartog" <anonymous@discussions.microsoft.com> wrote in message
news:B9674A54-AEF7-4A8F-B3A6-B9B49E05EA74@microsoft.com...
> I created an installer package which has been installer by several
clients. Now I want to create a new version. I increased the version number
and changed the upgrade code of the installer package and set the
RemovePreviousVersion property to True and set the
DetectNewerInstallerVersion to True as well.
[quoted text, click to view] >
> I have several registry setting setup in the registry editor. However if
the client has a previous version of the application installed I want the
system to remember those settings and not overrige them. Because the
RemovePrevioiusVersion property is set to True the system removes all
setting after which they are lost. However if I dont set this property to
true the system willl install 2 version of the application on the target
machine.
[quoted text, click to view] >
> How can I create a package that overrides (or removes) the old version but
doesn't override the registr values so that previous configuration settings
will be maintained? I spend many days trying to find a solution but haven't
had much luck. Also it must be possible to use this package as the first
installer meaning that if the client never had the application installed
before, he can run the setup to install the application. In other words it
is not just a patch for older versions.
[quoted text, click to view] >
> Many thanks, Paul