Note: there is a difference between 4413 and 3736. The 3736 makes sense as a
variable because it’s intended to be used in paths on ExePackages and such like
that. I don’t see a scenario where the number of apply phases would ever be
used as a variable. Maybe as an InstallCondition or something… but that’s too
late (IIRC, conditions are evaluated during Plan). <smile/>
Anyway, that’s the difference.
Also, to be clear, the reason the bug sat untouched for so long is that no one
is working on it. There are lot of bugs and feature requests. Waiting for
someone to work on your bug/feature request is playing the lottery. <smile/>
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
From: Sean Hall [mailto:r.sean.h...@gmail.com]
Sent: Wednesday, May 7, 2014 5:10 PM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] WIXFEAT:4413 Add WixBundleNumberOfApplyPhases
Neil - Maybe that's why it has sat untouched for so long? :)
As for being deprecated right out of the gate, <shrug />. Weird things happen
when you want backwards compatibility :)
On Wed, May 7, 2014 at 3:45 PM, Neil Sleightholm
<n...@x2systems.com<mailto:n...@x2systems.com>> wrote:
Thought I’d jump in as 3736 is mine. Other than the SQL install (probably the
worst installation package I have ever seen) I have not found another install
where this would be required. It would be handy for SQL but should we really
cater for such bad installs? Not at all sure how this applies to 4413.
Neil
From: Rob Mensching [mailto:r...@firegiant.com<mailto:r...@firegiant.com>]
Sent: 07 May 2014 19:38
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] WIXFEAT:4413 Add WixBundleNumberOfApplyPhases
The difference between this variable and the variable in #3736 (path to cache)
is that the path to the cache would be useful to provide on the command-line to
an ExePackage element. The number of times apply is going to be executed is
only really useful to the BA for its progress bar and thus not a good candidate
for a Variable.
I’ll let Bob weigh in on the way to incorporate this into WiX v3.x (if at all
<smile/>). It sounds like you agree the best change in WiX v4.0 is to enhance
the interface, which is cool. So, if this does get added as a variable in WiX
v3.x then I guess it gets added as deprecated right out of the gate (which is
kinda’ odd).
PS: I think pulling pull request discussions here is generally “A Good Thing”.
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
