Feature Requests item #1508973, was opened at 2006-06-19 19:27 Message generated for change (Comment added) made by boxcartootie You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1508973&group_id=105970
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: linker Group: Already Exists Status: Closed Priority: 5 Private: No Submitted By: mballou (mballou11) Assigned to: Derek (derekc) Summary: Allow Merge modules properties without MSM Guid Initial Comment: Using version 3.0.1814.0: If I define a merge module in a .wxs file, the resulting .msm will make all property names include the merge module extension. Normally this is what most users want, however there are cases where a merge module defines a command line driven component where this is not wanted. For example, I could have a component condition based on INSTALLTHISFILE being set. The end user could use a command line such as: setup.exe INSTALLTHISFILE Using current Wix tools, the component condition always gets the merge module GUID assigned, so the end user would have to type this: setup.exe INSTALLTHISFILE.8CFBE8E1_3EE8_4FF3_83D0_7049FFF15A6D The feature request is to have an optional tag that won't append the guid to the property name. Same option should go for entries in the Property table. ---------------------------------------------------------------------- Comment By: boxcar (boxcartootie) Date: 2006-12-13 13:18 Message: Logged In: YES user_id=1667759 Originator: NO I tried using IgnoreModularization and found out that it's been deprecated. It recommended that I use SuppressModularization instead - but I'm not sure how to use this with properties? For an example, I'm using a property that is set by the main msi, in my msm file (so this isn't created in my property table in the msm). How do I set it to suppress adding the GUID to the end of the property in this case? If you have an example of how to use SuppressModularization with a property, that would be great. Thanks. ---------------------------------------------------------------------- Comment By: Derek (derekc) Date: 2006-06-20 03:25 Message: Logged In: YES user_id=518766 This feature already exists. Please take a look at the IgnoreModularization element. Please note that this really isn't the cleanest way to support this functionality. There are at least 2 better solutions: 1. The MSI developer could use a type 51 (I think) CA to set the merge module's property from another more user-friendly property. 2. Stop using merge modules if you don't ship them to external customers. Internally use wixlib's and you can completely avoid modularization altogether. The problem with turning off modularization for items is that it opens you up to collisions between your authoring and that of the msi developer. If you control the msi so tightly that you can guarantee this will never happen, then using wixlib's is a far superior solution, and if its out of your control, using a type 51 CA is the most flexible and least risky option. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642717&aid=1508973&group_id=105970 ------------------------------------------------------------------------- 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-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
