|
I’d like to propose replacing the
<IgnoreModularization /> element with more specific “SuppressModularization”
attributes on the <Property /> and <CustomAction /> elements.
This basically allows the developer to suppress modularization for the 2
specific scenarios in which we currently know about the need to suppress
modularization. It would look like this: <CustomAction Id=”MyTableDrivenCustomAction”
SuppressModularization=”yes”
… /> Here’s why it’s needed in either case: CustomAction – table-driven CAs cannot be modularized
due to the fact that the table for the CA is shared across all merge
modules. For this reason, custom actions which work against custom tables
should not be modularized in merge modules. Property – although we advise against it, some users
want to refer to properties from a merge module in their main setup.
Sometimes doing this requires the property to not have an appended guid. Let me know what you think J Thanks, Derek |
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
