I might think a generic implementation to support this scenario of allowing
users to define public property values on the command line and/or in a single
xml file would involve a customAction sequenced to process right up front
during install/unstall and simply read the one per line property=value settings
from the public property "PROPERTYSETTINGS" defined xml file path and applied
them to the msi session object exposed public properties.
Would you think a person would have to create an extension or simply a custom
action managed (javascript or dtf managed msi library implementation) that gets
sequenced to process b4/after ??? to enable this?
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 29, 2008 1:44 PM
To: Robert O'Brien
Cc: 'wix-users@lists.sourceforge.net'
Subject: Re: [WiX-users] does current wix drop provide support for a public
property such as "msiexec /i myservicedeliverable.msi
propertySettings=environmentSpecificPropertySettings.xml ..."?
Robert O'Brien wrote:
does current wix drop provide support for a public property such as "msiexec /i
myservicedeliverable.msi propertySettings=
environmentSpecificPropertySettings.xml ..." where
environmentSpecificPropertySettings.xml consists of a single public
property=value pairs on each line that you might have otherwise set directly on
the command line but would prefer to keep them all in xml file so as to remove
changes of command line entry mistakes.
Not today.
--
sig://boB
http://joyofsetup.com/
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
