As part of installing our application, we deliver a merge module (our application includes an API, and the MSM is to enable our customers to create a Visual Studio deployment project for an application of their own written against our API).
It looks as if the MSM is internally compressed, because its size is less than that of the DLLs it contains. This has bad consequences when we try to build a patch for our application and the patch needs to update the installed MSM: the patch comes out very large, presumably because compressed files don't diff well. Is there any way to improve this situation? We can't use WiXlibs, because we don't want to insist that our customers use WiX to build their installers. Is there such a thing as an "uncompressed MSM"? Thanks in advance for any help anyone is able to offer! -- Cheers, John ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
