I have an installer for a product with an optional Office 2003 Addin
that requires the Office 2003 PIAs, and I'm trying to figure out how I
can install the assemblies only if the component is selected in the
feature tree. A bootstrapper will launch the PIA MSI beforehand,
wouldn't it?
I'm currently taking a look at the CC addin that Rob blogged about here
http://blogs.msdn.com/robmen/archive/2006/06/20/641202.aspx , but I have
a feeling that this is going to install the PIAs, then run the addin
setup.
Is there an MSM for the PIAs that I could use instead? That way, the
module could be a component of the optional feature. As an alternative,
I'm thinking about checking the registry to see which Office
applications are installed. Another possibility would be to run a
custom action to actually shell out and run msiexec on the included
package, but that seems a little messy for the end user (although I
suppose it could run silently).
Any suggestions on how to do this?
Thanks,
Chris
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
