On 21-Jan-15 16:29, Rob Mensching wrote:
Isn’t this what we’re discussing? Different ways to solve the patching
problem? I totally agree we haven’t hit consensus.
Right -- talking is how we get there. In person, this would be a shorter
conversation with people swapping positions between Visual Studio on a
laptop and multiple colors of pen at a whiteboard. :)
We’ve worked our way to a big question, the “higher level model” in
Bob’s words, of how to make patching really work, instead of the
disconnected set of tools we use today. I suggested we maybe should
consider the MSBuild targets to get there and I think Bob agreed
that’s a good place to start…
For sure. Mostly it's a question of whether we keep using single-purpose
tools wrapped in targets or we start moving more logic into
tasks/targets (or other higher-level tools that are then wrapped in
targets).
Sorry if the process takes a little bit to get there. Patching is both
one of the hardest parts of the Windows Installer and the least
developed in the WiX toolset. I expect we still have quite a bit of
ground to cover to get to an answer. Do you agree?
As usual, we have the right tools to support everything that MSI
supports, even if it's not the simplest to execute on.
Right now we're missing information. Can we easily adapt to using
.msi+.wixpdb pairs inside pyro? Peter added the admin-image stuff so
that points to yes but for some reason I'm not feeling confident.
--
sig://boB
http://joyofsetup.com/
------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
