> UpgradeVersion/@Property attribute to conditionalize them. Use
> UpgradeVersion/@OnlyDetect="yes" to avoid uninstalling the products.
> > 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.
The D3DX redist actually comes with a setup.exe, which I used to chain
with when using the VS Deployment project, so it sounds like this would
still serve.
> Yes, but not mixing both x86 and x64. MSI allows a package to target
> only one platform, so you'd need two packages.
I see. But I can make both packages part of the same product, and
conditionalize them on target platform, right?
> > 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,
> please. I suggest installing the file to a Program Files directory, then
> creating a shortcut to it.
OK, that will probably work, although it feels a little icky. Where's
/usr/local/doc when you need it? :-)
Thanks for your help.
jw
--
View this message in context:
http://www.nabble.com/Bewildered-and-confused-%28installing-multiple-versions-of-an-application-plug-in%29-tp16475968p16495151.html
Sent from the wix-users mailing list archive at Nabble.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
