Re: [WiX-users] Understanding component states

2009-09-09 Thread Don Pratt
? There are known >>> >> issues >> >>> with upgrades when RemoveExistingProducts is sequenced "too early" for >>> Windows Installer's interface to those technologies (fusion). >>> >>> You are sure this is a major upgrade.

Re: [WiX-users] Understanding component states

2009-09-04 Thread Ranganatha H C
, correct? > > > > -Original Message----- > > From: Wilson, Phil [mailto:phil.wil...@wonderware.com] > > Sent: Tuesday, September 01, 2009 3:18 PM > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Understanding com

Re: [WiX-users] Understanding component states

2009-09-01 Thread Don Pratt
or upgrade. The ProductCodes are different between > the two packages, correct? > > -Original Message- > From: Wilson, Phil [mailto:phil.wil...@wonderware.com] > Sent: Tuesday, September 01, 2009 3:18 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re

Re: [WiX-users] Understanding component states

2009-09-01 Thread Blair
ion for Windows Installer XML toolset. Subject: Re: [WiX-users] Understanding component states I read that to mean that the component is already installed and doesn't need updating from your new setup, perhaps because the versions are identical. Your RemoveExistingProducts is probably seque

Re: [WiX-users] Understanding component states

2009-09-01 Thread Wilson, Phil
I read that to mean that the component is already installed and doesn't need updating from your new setup, perhaps because the versions are identical. Your RemoveExistingProducts is probably sequenced to run at the end of your install, so it's applying update rules. In some cases you might see