On 3/22/2010 10:53 AM, John Aldridge wrote:
> so in this case the MSM /is/ the actual file, isn't it?
Indeed, that makes a difference. Merge modules must use an embedded
cabinet, per the MSI SDK. WiX doesn't offer explicit control over the
compression level in authoring, but the code appears to
On 22/03/2010 14:36, Bob Arnson wrote:
> On 3/22/2010 9:40 AM, John Aldridge wrote:
>> 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
On 3/22/2010 9:40 AM, John Aldridge wrote:
> 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
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, becau
4 matches
Mail list logo
