Hi guys,
I’ve always thought that keeping cabs extern to the MSI file improves performance and reduces the amount of disk space used on the destination machine.

I need to sell this to my boss, but I don’t really know why it reduces the space used on the disk (something to do with where the package is cached?) or why it improves performance…

Can any one provide a more detailed argument for keeping cab files compressed externally to the MSI?

0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Hi Fuz!
As far as I know, keeping the cabs external improves the installation time from network as it doesn't have to copy (in temp directory) the whole package before starting the installation, it copy the .msi then starts installation and follows copying the needed cabs to extract the info/files.
The fact of using always internal cabs or always external cabs I think it shouldn't be that strict, instead of this, I should purpose a maximum of Kb per msi (internal cabs), and those that pass that maximum should be build in external cabs (per component or feature, whatever you like).

Hope it helps :)

Answered 02/28/2007 by: KrisBcn
Purple Belt

Please log in to comment
Answer this question or Comment on this question for clarity