? 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.
, 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
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
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
: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Understanding component states
Hi,
I'm having trouble understanding why one component is failing to get
installed. I'm doing a major upgrade, and this component exists in both
the old and new versions
Hi,
I'm having trouble understanding why one component is failing to get
installed. I'm doing a major upgrade, and this component exists in both
the old and new versions of my package. If I manually uninstall the old
version and then do a normal install of the new version, the problem
compon
6 matches
Mail list logo
