I might just try that, but there could be a problem with that. First,
what would the consequence be of installing the PIAs on a system without
Office 2003 on it? Would it just add extra files to the GAC and be done
with it? Also, what about admin rights? If my installer doesn't
require administrative rights, but the PIA one does, I don't think I'd
even be able to offer the option of a non-administrative install for the
non-office components. Finaly, it looks like I'll have to support 2007
as well, which means installing both the 2003 and 2007 PIAs, which seems
to be kind of a waste.
I'm not saying that including the MSI in the bootstrapper is impossible,
just that it seems like there'd be a more elegant solution to the
problem.
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilson,
Phil
Sent: Thursday, March 29, 2007 2:15 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Conditional Install of the Office 2003 PIAs
I don't think it's worth the added complication. Just install the PIAs
in the bootstrapper.
Phil Wilson
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris
Bardon
Sent: Thursday, March 29, 2007 10:48 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Conditional Install of the Office 2003 PIAs
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
