|Subject:||Keeping merge modules separate|
|Posted by:||Monty (firstname.lastname@example.org)|
|Date:||Sun, 16 Sep 2007|
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.