This may be more of a general Windows Installer question than a WiX question.
I have a deployment group asking if there is any way to make site-specific installation any easier than the "msiexec command-line magic" or "Orca voodoo" that transforms seem to require. Notably, this is for sites that are not using GPO-style deployment, since Windows takes care of applying the transforms in that case. After some initial research, I am beginning to think the only other options would be a transform-aware bootstrapper, or just building a custom MSI for each site. Since they always have exactly one transform for the product in question, the first thing I (perhaps foolishly) tried was adding the TRANSFORMS property to the Property table of the MSI, with a value along the lines of "@SiteSpecific.mst" (with such an MST in the same folder as the MSI). As you might expect, this (and various variations thereof) had no discernible effect. Any thoughts would be much appreciated. Thank you, David Cramlet decram...@gmail.com ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
