jwatte wrote: > I think I know how to do 0) using RemoveExistingProducts. >
Yes. > I don't quite know how to do 1) -- I know how to use FindExistingProducts, > but not how to apply the findings to 2). > Create components for each one and use the properties in each UpgradeVersion/@Property attribute to conditionalize them. Use UpgradeVersion/@OnlyDetect="yes" to avoid uninstalling the products. > I'm a little hazy on 3). It only needs to be done once, even if multiple > versions of the DLL are installed. Is putting these files in a subfolder of > the temp directory, and then chaining out to the EXE the right thing to do? > That requires a chainer. You can't install an MSI as a custom action of another MSI. > 4) I can do this using Merge in my Product, I believe? > Yes, but not mixing both x86 and x64. MSI allows a package to target only one platform, so you'd need two packages. > 5) How do I handle the case of "current user" vs "all users" when it comes > to documentation? Putting it on the desktop, or the user's documents folder, > used to generate a warning about this in the Visual Studio deployment > project set-up. > The problem with installing files to users' directories is that they generally feel that any files there are theirs to do with as they please. I suggest installing the file to a Program Files directory, then creating a shortcut to it. -- 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
