5:52 -0300
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Practical use of wixlibs
>
> That's extremely enlightening. I thought having two components in
> different products with the same GUID but different installation
> directories would be a blatant break of com
e sink.
>
> --
> Nicolás
>
> 2013/10/2 Blair Murri :
> > See
> > http://blogs.msdn.com/b/heaths/archive/2009/12/21/about-shared-components.aspx
> >
> >> From: nicolas.alva...@gmail.com
> >> Date: Tue, 1 Oct 2013 00:51:36 -0300
> >> To: wix-user
com/b/heaths/archive/2009/12/21/about-shared-components.aspx
>
>> From: nicolas.alva...@gmail.com
>> Date: Tue, 1 Oct 2013 00:51:36 -0300
>> To: wix-users@lists.sourceforge.net
>> Subject: [WiX-users] Practical use of wixlibs
>>
>> I can't find any documentati
See
http://blogs.msdn.com/b/heaths/archive/2009/12/21/about-shared-components.aspx
> From: nicolas.alva...@gmail.com
> Date: Tue, 1 Oct 2013 00:51:36 -0300
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Practical use of wixlibs
>
> I can't find any document
es and went with wix libs.
From: "Nicolás Alvarez"
Sent: Monday, September 30, 2013 10:58 PM
To: "General discussion for Windows Installer XML toolset."
Subject: [WiX-users] Practical use of wixlibs
I can't find any documentation on best-practices wh
I can't find any documentation on best-practices when creating either
merge modules or wixlibs, only procedure documentation on how to
create them.
Let's say I create a wixlib (or msm) with multiple components that
make up a large C++ library. Someone making an application with that
library can th
6 matches
Mail list logo
