Actually, no. Say I have two wixlibs for two different features. I run
heat as a prebuild on both libs (so in total it is run twice) with the
-cg option which very nicely generates componentgroups, but the ID's for
each directory are things like 'folder1'. Now when both libraries have
directories with the same Id it is there that I run into trouble. 

-Nick

-----Original Message-----
From: Markus Karg [mailto:markus.k...@gmx.net] 
Sent: 03 November 2009 18:21
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Fragments or Merge Modules?

For me this more sounds like a bug in heat. IDs should be GUID --
*unique*
IDs.

Regards
Markus

> -----Original Message-----
> From: Nick Ball [mailto:nick.b...@grantadesign.com]
> Sent: Dienstag, 3. November 2009 16:07
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Fragments or Merge Modules?
> 
> I've had a problem using wixlibs in that auto-generated (heat.exe)
> libraries can end up having the same ID's for components, which then
> fails to build. This doesn't happen with merge modules - which is what
> I've ended up doing.
> 
> -N
> 
> -----Original Message-----
> From: Blair [mailto:os...@live.com]
> Sent: 02 November 2009 21:02
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: Re: [WiX-users] Fragments or Merge Modules?
> 
> More-or-less yes, you have it right.
> 
> There are several servicing issues related to Merge Modules, and some
> of
> those issues are carried into the way that WiX incorporates Merge
> Modules
> (making them even harder to deal with than they already would have
> been,
> especially as relates to patching/patch generation).
> 
> You can create "binary" wixlibs, which are compiled fragments that
> carry
> the
> files they otherwise incorporate by reference in the wixlib itself,
> making
> them have all the advantages of merge modules except the portability
> with
> other toolsets.
> 
> The typical decision path is: prefer either fragments or wixlibs over
> merge
> modules when you don't need to incorporate the shared code with
non-wix
> toolsets.
> Note that wix 3.5 and 3.0 can share the same wixlibs, while wix 2.0
> can't
> share the same libs with 3.x (or the same source code without some
> transformation either).
> 
> -----Original Message-----
> From: Markus Karg [mailto:markus.k...@gmx.net]
> Sent: Monday, November 02, 2009 12:07 PM
> To: 'General discussion for Windows Installer XML toolset.'
> Subject: [WiX-users] Fragments or Merge Modules?
> 
> If I understand correctly, there are two ways to modularize my setup:
> Fragments and Merge Modules. So the question is: Which one to use?
> 
> 
> 
> For me it looks like Merge Modules being a more heavy weight solution,
> but
> the benefit is that those are a product-independent standard (i. e.
> InstallShield or Wise can use them, too), while Fragments are more
> light
> weight, but can be used only by WiX. Is that correct? Or did I missed
> the
> point? Maybe there is a more essential difference (besides the fact
> that
> a
> Fragment is a *source object* while a Merge Module is a *binary
> (compiled
> and linked) object*)?
> 
> 
> 
> What is the typical decision path (when to prefer Fragments over Merge
> Modules and vice versa)?
> 
> 
> 
> Thanks
> 
> Markus
> 
>
-----------------------------------------------------------------------
> -
> ----
> --
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart
> your
> developing skills, take BlackBerry mobile applications to market and
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 
> 
> 
>
-----------------------------------------------------------------------
> -------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart
> your
> developing skills, take BlackBerry mobile applications to market and
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users




------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to