When I use heat, it generates dir/comp/file ID's such as
cmpXXXXXXXXXXXXXXXX
dirXXXXXXXXXXXXXXXX
filXXXXXXXXXXXXXXXX
If I omit the File/@Id attribute I get a different transformation pattern
autogenerated. Is there a way to make it make the autogenerated flavor be
like the way heat does it?
Also when I try to use autogenerated componentID/Guids in merge module projects
I get an error message saying the file isn't rooted in ProgramFilesFolder.
Eventually it will be though since we wire all of our modules up to
targetdir\installdir. I found a hackish way around this error ( declare a
Directory of ProgramFilesFolder with a DefaultDir of . and put it in the
heiraachy ) but I was wondering if there is a better way here.
Basically I'm trying to come up with a way of writing merge modules that have
as much autogenerated id's and guids as possible to minimize the mistake of
component rule violations and such.
Thanks,
Chris
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
