Hi,
Our full setup file can be up to 85MB in size, but much of this is runtimes (vb6, .NET 2, VCRT 2008, VCRT 2010, etc.); with MSI installations I would like to know what I can do to make our installer packages smaller.
With our old installer we had a Full Setup that was our program EXEs, DLLs, and supporting Data files, plus all required runtimes. Our customers have to install this as their initial install, to ensure they have the required runtimes as well as answer some configuration/settings prompts about. Then, after bug fixes are ready we provide an Update install file that has our Program EXEs, DLLs and supporting data files, but it has NO runtimes. This often shrinks our Update installer package down to about 20MB, so a substantial savings in download time / disk cost / installation speed etc.
How does one go about this with MSI technology (without using MSP; which we cannot use as our app violates one of the many rules that enable MSP to work)?
Alos, how would do I make that Update installer package (again, not MSP-based), so that if our app is already installed and the user wants to install our the update they only get minimal dialogs (not the full setup dialogs). Our full setup collects all the other details, such as where the app should be installed, the user's name, etc., etc.
Thanks in advance.
FOLLOW US
Get the latest news in Application Packaging