WIX GUID question
Jeffrey Altman
jaltman at secure-endpoints.com
Tue Apr 22 15:23:33 EDT 2008
Kevin:
As was stated previously, the NSIS install would bundle vcredist_x86.exe
and execute it.
The MSI (WIX) installer would use the merge modules.
Jeffrey Altman
Kevin Koch wrote:
> The IFDEF CL_1400 sections of kfw-fixed.nsi try to copy the DLLs from
> SYSTEMDIR instead of from c:\WINDOWS\WinSxS, where they actually are.
>
> I'm curious why NSIS can't run vcredist_x86?
>
> Kevin
>
> -----Original Message-----
> From: Jeffrey Altman [mailto:jaltman at secure-endpoints.com]
> Sent: Monday, March 31, 2008 11:20 PM
> To: mayer at ntp.isc.org
> Cc: Kevin Koch; kfwdev at mit.edu
> Subject: Re: WIX GUID question
>
> Danny Mayer wrote:
>> Kevin Koch wrote:
>>> When I install from the .msi or .exe on a bare XP SP2 VM, msvc*80*.* are
> not
>>> installed. Where/how is CL1400 / CL_1400 supposed to be defined?
>>>
>>> Kevin
>>>
>> You ship the redistributable vcredist_x86.exe which the client needs to
>> install. Your installer can just run it.
>>
>> Danny
> That is how the NSIS installer would do it but not the MSI. For the MSI
> we use merge modules.
>
> _______________________________________________
> kfwdev mailing list
> kfwdev at mit.edu
> http://mailman.mit.edu/mailman/listinfo/kfwdev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3355 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mailman.mit.edu/pipermail/kfwdev/attachments/20080422/630eed86/attachment.bin
More information about the kfwdev
mailing list