Thanks everyone for all your help, it's now working. I found one bug in my code where <ComponentGroupRef Id="WebConfigSetupComponents" /> was referenced in multiple features (one conditioned on upgrade and one not), and once that was cleaned up, I found I could place the NOT UPGRADEFOUND condition back on each component as per Bob's suggestion, and this time it worked!
I didn't have to worry about conditioning the SchedXmlFile in the execute sequence, which means upgrades should be able to make web.config changes also. Just in case someone else runs into this issue, the approach was to: - Add component to feature which is always executed (Absent=disallow) - Add condition to component containing XmlFile to only execute on new installs (NOT UPGRADEFOUND or whatever property you create). On Thu, Sep 24, 2009 at 1:26 AM, Blair <os...@live.com> wrote: > The Request is the expected-intended state (based on conditions and parent > features). Null means it shouldn't be touched. I'm interested in knowing why > it says Installed: Absent on the upgrade. I just checked and all my components say "Installed: Absent" in first the InstallValidate, and then "Installed: Local" in the second InstallValidate. Guess I need to grep the logging output more, but what is interesting is now in the first InstallValidate, it reports "Request: Local" instead of the "Request: Null" it was reporting before. Regards Si ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
