It's not that I want to know where it was previously installed. It's that I want to know if a configuration file already exists in the path the user selects (INSTALLDIR). If the configuration file already exists, I don't want to give the appearance that it can be changed; i.e. I am presuming that that configuration file points to an orphaned configuration that the user wants to adopt again.
Ex. - By default INSTALLDIR is set to C:\Program Files\MyApp - User changes the installation directory to C:\MyApp - User specifies the file store to be D:\MyApp\FileStore - The application is installed and the configuration file is written containing FileStore=D:\MyApp\FileStore - User uninstalls application [1]; configuration file remains. - User installs application again (new version) - User changes installation directory to C:\MyApp - Installer should detect that the configuration file already exists in C:\MyApp and not present the UI to specify the file store location. - The application is installed but the configuration file is not overwritten. [1] He didn't realize that he could just upgrade using the new installer instead of manually uninstalling the old version first. -- Bill Arnette www.starwitness.com -----Original Message----- From: Brian Simoneau [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 31, 2007 2:15 PM To: Arnette, Bill; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] AppSearch during UI You could write a permanent registry entry containing the path that the user selected, then read the registry entry when the install is run again to find out where it was installed before. -Brian Simoneau -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arnette, Bill Sent: Tuesday, July 31, 2007 10:50 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] AppSearch during UI We are trying to mitigate an admittedly pathological case during installation. 1. User installs application to other than default directory. The installation installs a permanent, never-overwrite configuration file which (among other things) specifies a file store [1] path which is specified by the user during installation via a dialog. [2] 2. User later uninstalls the application. Because the configuration file is permanent, it is not deleted. 3. User installs the application again and specifies the same installation location as the last time it was installed. But this time, since the configuration file exists, I don't want to show the UI that allows them to specify the file store location and I want to use the old configuration file (which never-overwrite already takes care of). The problem is, I can do the AppSearch before the UI to locate the configuration file in the default installation directory. But if the user changes the installation directory, how do I determine if the configuration file exists in that new path in order to skip the file store configuration UI? The only thing that comes to mind is to write an AppSearch-like CA that looks for the file in the new path. Is there an easier way? [1] The file store is the place where large media files are stored outside of the XML "database". [2] I hear you! The installer should not do configuration. BUT, the application also allows optional installation of sample data. That sample data needs to go in the file store which is specified in the configuration file. So there needs to be some level of configuration in the installer. -- Bill Arnette Principal Software Developer StarWitness Business Unit Signalscape, Inc. www.starwitness.com ------------------------------------------------------------------------ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
