Here is the scenario. We do the initial installation. Then little if any of
the "properties" (there are about 10 that basically define the app, server
name(s), user name, SMTP server, etc.) change. But the code changes so we
"release" with new features and bug fixes fairly regularly. I want to build
a installer package that goes through the initial installation (brings up a
dialog prompting the user to enter the 10 or so properties) if the app is
not installed. Then if the app is installed it retrieves these "properties"
(My thinking is that we would store them in the registry but is these
information stored in the installer database? How do I access it? Is it a
persistent database? I have only seen references that require a .msi) and
skips the custom UI and proceeds with the installation. I have read somewhat
about <Upgrade> but I am not entirely clear. If I change the version of the
.msi package what is the trigger or flag to the installation package that
tells me to read the properties from the registry and not prompt the
user/installer for these values? I somewhat understand you can fire off a
custom action but what if all I want to do is set all of the properties
based on the registry settings and skip my custom dialog?
Thank you for any suggestions.
Kevin
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
