Christopher Painter wrote: > I'm afraid you lost me there. Just about everything inside the MSI > engine can be one outside of MSI.
We were discussing simple property persistence. MSI has an equally simple declarative pattern: Write it to the registry during installation, read it back via AppSearch; if it's not there, it hasn't been written yet but that's OK because MSI does the right thing during AppSearch. Purely declarative, no custom actions. > I know everyone likes to say configuration data is a pain.... but > imagine how painless it would be if MSI/MMC/AD/GPO had this type of > built-in story and ISV's were supporting it as part of their > deployment story. Configuration is distinct from installation. Most configuration data needs to be per-user which doesn't fit the typical per-machine/first-run installation model of MSI. -- 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
