On 17-Jun-13 11:08, Hoover, Jacob wrote:
I haven't had a chance to look at the code but the concept is sound. Normally, I'd say you'd want to require the user to opt-in to using an .ini file (e.g., by requiring it as a command-line argument). But being able to "transform" the bundle just by dropping an .ini next to the bundle .exe on a network share is too cool. :)I took a stab at this over the weekend (IniFileSearch, not reading another bundles variables) and I have a functional branch at https://wix.codeplex.com/SourceControl/network/forks/jchoover/Wix?branch=IniFileSearch. I'd like to know if the ability to read arbitrary in files from a bundle would be considered for 3.8. I would need to flesh out the IniFileSearch a bit more in the compiler, to allow it to be a child of a few more of the search elements.
That said, a common requirement is to be able to mix and match sources: GPO, .ini file, command-line arguments, maybe even registry. Getting precedence right is app-specific, so probably something to keep out of the engine.
-- sig://boB http://joyofsetup.com/
------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev
_______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs