Are there any "best practices" for managing a larger WiX project in
VS2008? I need to create four MSIs (32/64 bit versions of two releases,
differing only by configuration files.).
* 32-bit specific WiX project containing 32-bit libraries from
developers
* 64-bit specific WiX project containing 64-bit libraries from
developers
* Generated WiX code (massaged heat output).
* Common files
* Configuration files for release A and release B. These have
identical file names, just different content.
I'm assuming that I need the following in the VS solution:
* Four WiX projects, one for release A and B, 32- and 64-bit.
* A WiX library for the generated code. (This is huge and takes
quite a bit of time.)
* A WiX library for the common files.
* A WiX library for release A configuration.
* A WiX library for release B configuration.
I assume that I do this:
* Add the WiX library projects outputs to the WiX projects
"References".
* Set the WiX project dependencies to the WiX library projects.
* Use different GUIDs for all of the WiX project upgrade, product,
etc. GUIDs.
Is that it?
Am I overlooking anything?
Thanks!
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
