First step is to describe the location of the INI file in such a way as to enable using the IniFileSearch element. Easiest may be to have your bootstapper supply a property to the MSI with the INI file's location.
-----Original Message----- From: John H. Bergman (XPedient Technologies) [mailto:john.berg...@xpedienttechnologies.com] Sent: Thursday, November 12, 2009 7:23 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] setup.ini... (Wix 3.5) Has anyone used Setup.ini to configure the public properties of an install? I am having some difficulty getting this to work. I am using a bootstrapper that installs .NET 3.5SP1, and then an MSI that has public properties deailing with things like Server names, user accounts, etc. I cannot seem to get the installers to use an .ini file that contains this information? Is there some magic voodoo to this? ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
