David- That's the "correct" way to do it and if you are redistributing the merge module to a third party ( does anyone do that anymore?? I wouldn't! ) that is what should be done. But I've found in my day job where my merge modules are just that way to do the equivilant of binary wix libraries with other tools like InstallShield for purposes of breaking the installer out into chunks that it's easier to just come up with a standard set of internally used property names and suppress them across all of the merge modules. This makes it a lot easier to assemble all of the modules together especially considering InstallShield only applies property configuration to the first module merged and not the child modules that are merged.
Chris Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me ----- Original Message ---- From: David Watson <dwat...@sdl.com> To: General discussion for Windows Installer XML toolset. <wix-users@lists.sourceforge.net> Sent: Tue, November 16, 2010 5:45:22 AM Subject: Re: [WiX-users] avoiding GUID decoration in merge module propertyname Hi, If you own the merge module you can make the property alterable. I did an example with a property called DBNAME a while back... In the merge module add something like this. <Configuration Name="DBNAME_Property" Format="Text" NonNullable="yes" DefaultValue="defaultValue" /> <Property Id="DBNAME" Value="unset"/> <Substitution Table="CustomAction" Row="setdbname" Column="Target" Value="[=DBNAME_Property]" /> <CustomAction Property="DBNAME" Value="[DBNAME]" Id="setdbname" Execute="immediate" /> <InstallExecuteSequence> <Custom Action="setdbname" After="LaunchConditions" /> </InstallExecuteSequence> Add to the main wix <Property Id="DBNAME" Value="adefaultvalue" /> <Merge Id="blob" DiskId="1" Language="1033" SourceFile="..\mergey\mergey.msm"> <ConfigurationData Name="DBNAME_Property" Value="[DBNAME]" /> </Merge> -----Original Message----- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 16 November 2010 04:05 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] avoiding GUID decoration in merge module propertyname Property/@SuppressModularization documentation says: SuppressModularization YesNoType<mk:@MSITStore:C:\Program%20Files%20(x86)\Windows%20Installer%2 0XML%20v3.6\doc\WiX.chm::/html/wix_xsd_simple_type_yesnotype.htm> Use to suppress modularization of this property identifier in merge modules. Using this functionality is strongly discouraged; it should only be necessary as a workaround of last resort in rare scenarios. On Mon, Nov 15, 2010 at 6:09 PM, Alan Sinclair <alan.sincl...@citrix.com>wrote: > I need to set a property "MYSPECIALDATA" in a merge module, but the > property name cannot have a guid appended because MYSPECIALDATA is read > later by the consuming MSI (which doesn't know guids). > > Is there any way this can be done in WiX 3? I'd like to use a type 51 > custom action to set the property, but can't get an undecorated property > name; it doesn't seem to make a difference whether the property name is > defined outside of the custom action or not. > > I'd hate to have to script up removing the guid after the merge module is > compiled! > > thanks > Alan > > > > ------------------------------------------------------------------------ ------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today > http://p.sf.net/sfu/msIE9-sfdev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------ ------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
