Re: [WiX-users] prevent component removal on major upgrade

2010-10-05 Thread gapearce
Well, after much goofing around, I think UPGRADINGPRODUCTCODE check is working for what I need. My design is wrong from the start to re-order removal of existing products... but I will design the next installer with this method in mind. Thanks so much for your help Blair... and the great explana

Re: [WiX-users] prevent component removal on major upgrade

2010-10-04 Thread Blair
et Subject: Re: [WiX-users] prevent component removal on major upgrade Oh, actually that won't work either. I'm trying to keep the folder around: It already exists. Changing the level to zero prevents it from getting installed - it doesn't prevent the original folder from getting

Re: [WiX-users] prevent component removal on major upgrade

2010-10-04 Thread Blair
use Feature and/or Component state, not installation state properties, to schedule custom actions that change machine state. -Original Message----- From: gapearce [mailto:mr_gapea...@yahoo.com] Sent: Monday, October 04, 2010 4:05 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-us

Re: [WiX-users] prevent component removal on major upgrade

2010-10-04 Thread gapearce
Sorry - just found this link to explain RemoveExistingProducts: http://msdn.microsoft.com/library/aa371197.aspx I am thinking of trying this, but this says that the RemoveExistingProducts needs to be scheduled 'between' the InstallExecute action, or the InstallExecuteAgain action, and the Instal

Re: [WiX-users] prevent component removal on major upgrade

2010-10-04 Thread gapearce
Oh, actually that won't work either. I'm trying to keep the folder around: It already exists. Changing the level to zero prevents it from getting installed - it doesn't prevent the original folder from getting deleted, right? Now I'm really confused. -- View this message in context: http://wi

Re: [WiX-users] prevent component removal on major upgrade

2010-10-04 Thread gapearce
Hi Blair, and thanks for the response. What you describe is an advanced functionality that I'm currently incapable of implementing. I just don't know enough about this stuff to even try that right now ... Is there an example of the latter suggestion that you might be able to provide? (i.e. "

Re: [WiX-users] prevent component removal on major upgrade

2010-10-04 Thread Blair
Change your upgrade order (install upgrade, then remove old), but that requires that you carefully follow the component rules. The only other thing I can think of (if you really can't change the upgrade operation order) is this: you may try forcing the level of the feature containing your non-upgr