M
Michael Kleehammer
During my initial install, the user enters some information (ODBC settings)
that are written to the registry using public properties. If the user
attempts to modify their install, I can repopulate the dialog from the
registry, but any changes the user makes are not written to the registry.
The registry settings are packaged into a single component with the
existence of the registry key used as the 'key' for the component. I
suppose the new values are not written since Windows Installer is designed
to add or remove components/features, but not to modify them.
Is there a way I can force WI to write the registry values even if they are
already there? Is there an internal property I can set in maintenance mode
to force a particular component (the registry values) to be re-installed?
Thanks,
Michael
that are written to the registry using public properties. If the user
attempts to modify their install, I can repopulate the dialog from the
registry, but any changes the user makes are not written to the registry.
The registry settings are packaged into a single component with the
existence of the registry key used as the 'key' for the component. I
suppose the new values are not written since Windows Installer is designed
to add or remove components/features, but not to modify them.
Is there a way I can force WI to write the registry values even if they are
already there? Is there an internal property I can set in maintenance mode
to force a particular component (the registry values) to be re-installed?
Thanks,
Michael