On 22-Jan-15 13:55, Tunney, Stephen wrote:
You’re suggesting that we remove the melt and torch steps and have
pyro encompass **everything** that patch building requires? Or is
this the Pyro MSBuild Task that you speak of?
The latter. We need the building-block tools (torch, pyro) but can build
tasks and targets on top of them.
If we move to a MSBuild style the only questions that really need to
be asked are:
RTM MSI paths
Upgrade MSI paths
Patch Families to create
Version
Type
I'm not talking about having MSBuild replace patch authoring. There's
too much there to do it all in the project. That could be an option for
a high-level, limited-scope kind of patching (i.e., no filtering).
Before that, we need tasks and targets that drive "normal" patching.
--
sig://boB
http://joyofsetup.com/
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
