Hi, I have a web application deployment project that creates a setup.exe
file and a .msi file. I have an msi file from a 3rd party vendor that is
rolled up into my msi making it ridiculously huge. I'm wondering if it's
possible using just VS 2005's deployment options to have the 3rd party's MSI
files stay separate from my own so that they could be downloaded separately.
Yes, I know they'll all need to be there for the initial install, but it
will make subsequent updates much quicker. Any thoughts? TIA.

Hi Monty,

This is a quick note to let you know that I am performing research on this
issue and will get back to you ASAP.

I appreciate your patience!

Sincerely,
Linda Liu
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

I'm assuming your subject line is correct and you're adding a merge module
into your setup, because you can't really rollup an MSI file into your MSI
file. If the vendor supplied only a merge module then it must be added into
an MSI setup like yours. Unless they supply a standalone MSI file you'll
have to include the merge module in something you ship, if not in your web
setup MSI then in another MSI you could create from that merge module.
--
Phil Wilson
[MVP Windows Installer]

[quoted text, click to view]

Thanks Phil.

Hi Monty,

After doing some research, I realize that we could not keep merge modules
separate from the main MSI package. Alternatively, if the 3rd party vendor
could provide MSI file instead of merge modules, you can install the MSI
package from your main MSI package. The following KB article explains how
to do this:

'How to create a nested .msi package'
http://support.microsoft.com/kb/306439

Hope this helps.

Sincerely,
Linda Liu
Microsoft Online Community Support

Unfortunately I only have merge module, so looks like I am stuck with a big
install package for now. Thanks for your research Linda, that is still good
to know!