I appreciate this wouldn't be trivial to arrange but I believe the benefits
would be worth it. I base this on the speed at which I have been able to
develop the extended BA, spending time breaking it out of the WiX build has
made it so much easier to work on.
Neil
From: Bob Arnson [mailto:[email protected]]
Sent: 18 February 2013 21:07
To: [email protected]
Subject: Re: [WiX-devs] Building WiX Code
On 18-Feb-13 14:22, Neil Sleightholm wrote:
There is an SDK for WiX so I would expect the extensions to use it
I think that's the root disconnect: The extensions that ship with WiX aren't
separate from WiX, so there's been no reason to build them separately. It's not
that I think they shouldn't or that it's a bad idea, just that that's not how
it's been done. So building them separately is reasonable -- but it can't break
the things that need to work for things that ship with WiX, such as versioning
and error numbers.
I'd add that breaking the build into separate partitions like this reduces the
extent to which the build can be parallelized. Minimizing that impact would
also be good.
Making all that work (as well as making the build output match the staging
output) is probably a 2.5 on a difficulty scale of 1 to 10.
--
sig://boB
http://joyofsetup.com/
------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
