I'm starting to build an installer for an application that includes a
number of VB6 authored OCX controls. It seems that the correct way to
capture COM registration data for these OCXs is to use 'heat file ...',
which seems to generate nice Wix fragments.
I want to call heat as part of the build process (rather than use its
output as a template and commit it to source control) so that if the OCX
interface changes, as it does from time to time, the fragment is
recreated.
Question 1: If I use the -gg argument to generate a GUID each time, does
it matter that the component is effectively a different component in
each build? I should note that currently, we only ever do major
upgrades.
Question 2: What is the best way to invoke heat as part of a build
process? I'm currently deciding whether to use make or msbuild to tie
everything together, and invoking heat from make is obviously quite
straightforward, but I'm less familiar with msbuild.
Cheers,
John
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
