I didn't think about it from that angle. All things considered, I can see how it's an understandable choice.
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: Blair <os...@live.com> To: General discussion for Windows Installer XML toolset. <wix-users@lists.sourceforge.net> Sent: Thu, July 1, 2010 2:14:39 AM Subject: Re: [WiX-users] Property Element Question This is my personal opinion, since I didn't write that code. However, given what I have seen of the code, it seems quite reasonable (at least to me ;-) ). Because the property "TEST" may be found in a Condition, a formatted field, or who knows where else a reference to the item may be within the module, you end up not knowing whether to modularize the reference to the property or not. If you don't allow the same label to be both, you eliminate that ambiguity. I stopped counting all the places in just the standard tables where modularized "things" could be found. It would require additional/different syntax to disambiguate these admittedly edge cases which would complicate both readability and code portability. -----Original Message----- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Wednesday, June 30, 2010 9:45 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Property Element Question Consider the following: <Module .....snip..... <Property Id="TEST" Value="1"></Property> <Property Id="TEST" Value="1" SuppressModularization="yes"></Property> </Module> WiX generates the error message Duplicate symbol Property:TEST found But I'm wondering if this was truely intentional or a bug in WiX? In the case of a merge module the SuppressModularization attribute causes a unique Property to be generated in the resultant MSM and it's conceivable ( a strech to be fair ) to need both TEST and TEST.GUID in the MSM. Anyone ever think about this before? I'm asking mostly because I'm in the process of writing some code which includes defining a dataset and declaring which columns should be part of the uniqueness constraint. Thanks, 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 ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
