Hi Bob,
I have discovered a few hours ago that SetInstallLevel to 1 in an
upgrade will actually refresh the Features and install only the features
that I want. Your suggestion would help if the setup type had 3 options:
Typical, Full, Custom. This setup has more levels and tuning
INSTALLL
Calin Iaru wrote:
> It should be only Administration because the setup resets the level
> of all other features to 0 when "Typical" is selected like this:
>AllowAdvertise="no">
>
>
That's not going to work. MSI evaluates feature conditions only once,
during CostFinalize. U
Hi Bob,
the package runs from the User Temp directory. The package code is
changed. I think there are two problems:
one - ADDLOCAL is not looking as expected when doing a typical
install because it's set to everything. But the typical
setup will actually install what I want. Maybe it's a
Please keep wix-users on the thread.
Calin Iaru wrote:
you're right. Now I need to find what is the cause of this problem. I
always change the version and product code
but somehow I get this message:
MSI (s) (14:48) [17:39:13:796]: Skipping RemoveExistingProducts action:
current confi
Calin Iaru wrote:
> I don't think there's a way to have a remove button implemented inside a
> major upgrade MSI package.
> At least not from WiX. WinDbg supports Upgrade and CustomUpgrade modes,
> which are somewhat
> helpful, but it seems that there are no samples (tutorials or other MSI
> dis
I don't think there's a way to have a remove button implemented inside a
major upgrade MSI package.
At least not from WiX. WinDbg supports Upgrade and CustomUpgrade modes,
which are somewhat
helpful, but it seems that there are no samples (tutorials or other MSI
distributions) like the one I nee
Hi Bob,
been there. I find that something similar is done with WinDbg.
Thanks to all for helping out. Keep you posted.
Best regards,
Calin
Bob Arnson wrote:
> Calin Iaru wrote:
>> I see that MigrateFeatureStates discovers that the features are
>> installed. Next, InstallValidate says t
Calin Iaru wrote:
> I see that MigrateFeatureStates discovers that the features are
> installed. Next, InstallValidate says that the feature is absent when
> the versions do not match (ie install with one MSI and uninstall with
> the other). RemoveExistingProducts is skipped in both cases (remov
EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Calin Iaru
> Sent: Thursday, September 28, 2006 12:17
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Upgrade and remove
>
> Short note:
>
> InstallValidate does not discover any of the Features as bei
rsday, September 28, 2006 12:17
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrade and remove
Short note:
InstallValidate does not discover any of the Features as being installed.
Calin Iaru wrote:
> Hi List,
>
>I have 2 MSI packages which are compiled with differen
Short note:
InstallValidate does not discover any of the Features as being installed.
Calin Iaru wrote:
> Hi List,
>
>I have 2 MSI packages which are compiled with different versions and
> different product code GUIDs. I want on the newer one to offer the
> possibility to remove the ins
Hi List,
I have 2 MSI packages which are compiled with different versions and
different product code GUIDs. I want on the newer one to offer the
possibility to remove the installation. How can I do this? I have tried
several times to trigger a Remove event on the new version, but I still
ha
12 matches
Mail list logo
