-Original Message-
From: Martin Kulov [mailto:mar...@kulov.net]
Sent: Tuesday, 10 May 2011 11:14 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] dependent features
Michael,
Any tips on how to implement compensating action on uninstall?
Should
and (e.g. start myapp.exe). It
will have the desired effect in the Start/Run dialog box however.
-Original Message-
From: Martin Kulov [mailto:mar...@kulov.net]
Sent: 10 May 2011 10:33
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] dependent featur
AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] dependent features
App Paths would be a neat way to solve this, if they meet all your
requirements. The "registration" lives in components that you can add to the
features.
http://msdn.microsoft.co
App Paths would be a neat way to solve this, if they meet all your
requirements. The "registration" lives in components that you can add to the
features.
http://msdn.microsoft.com/en-us/library/ee872121%28v=vs.85%29.aspx#reg_app
-Original Message-
From: Martin Kulov [mailto:mar...@kulov.
Message-
From: Martin Kulov [mailto:mar...@kulov.net]
Sent: Tuesday, 10 May 2011 11:14 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] dependent features
Michael,
Any tips on how to implement compensating action on uninstall?
Should I preserve the p
@lists.sourceforge.net
Subject: Re: [WiX-users] dependent features
Hi Michael,
That was something I was playing with. However your solution just nailed it!
One comment for the history - one should use public property like PATHADD
instead of PathAdd to make sure property is transferred between user and
osm...@baytech.com.au
> To: wix-users@lists.sourceforge.net
> Date: Tue, 10 May 2011 08:04:59 +1000
> Subject: Re: [WiX-users] dependent features
>
> Hi Martin
>
> You could build up a single property with the PATH entry you wish to add
> using a series of Type 51 Custom
Hi Martin
You could build up a single property with the PATH entry you wish to add using
a series of Type 51 Custom Actions. Each would add the path option for a
feature and be conditioned by the feature state. You then have a single
component (linked to you Register Environment Variables fe
Adam Langley wrote:
> How do I configure these 4 features so that if either (or both) of the 2
> websites that needs the GAC feature is chosen for installation, then the UI
> forces the user to select the GAC feature aswell? But if only the website
> that doesn't need the GAC assemblies is chosen,
9 matches
Mail list logo
