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
Sort of obscure not-detailed-enough half-mentions on MSDN?
For deep technical dives into Windows Installer Heath is my go-to resource.
> From: nicolas.alva...@gmail.com
> Date: Wed, 2 Oct 2013 15:45:52 -0300
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Prac
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 component rules and would just
not work. "Allowing uninstallation of shared component. Other clients
exist, but installed to a d
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 documentation on best-practices
Libs, binary libs, and merge modules are all about code structure and reuse.
I once worked for a company that at it's peak had 250 developers and 2 install
developers. Our business model was built around a concept called "Product
Line". Think if it like a car manufacturer who has different
5 matches
Mail list logo
