If we create a new syntax, we should consider how it fits with other bind 
properties. I'm inclined not to add a new syntax (there are already too many 
magical characters in !(bind.) variables). Enumerating all of the package names 
should be possible, so it shouldn't be horrible to compare the start of the 
string after "msiPackageProperty" with package names.

Or something like that. Better to do a bit of hard work in toolset than expose 
even more complex syntax to users.

From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Sunday, February 2, 2014 9:29 PM
To: wix-devs@lists.sourceforge.net
Subject: Re: [WiX-devs] Binder variables for MSI properties in a bundle

On 02-Feb-14 23:56, Sean wrote:

It seems like the tricky thing for implementing this will be how to deal with 
the dots, like Bob put in the feature (http://wixtoolset.org/issues/4298/).  As 
far as I can tell, package Id's have the same rules as MSI properties 
(http://msdn.microsoft.com/en-us/library/aa371245(v=vs.85).aspx<http://msdn.microsoft.com/en-us/library/aa371245%28v=vs.85%29.aspx>).
  How about !(bind.msiPackageProperty.packageId~propertyName), or some other 
special character between the package Id and the property name?
We don't want it to look too much like Perl. :) We could probably do some 
quoting, like with brackets or backticks.


--

sig://boB

http://joyofsetup.com/
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs

Reply via email to