Sometimes we do the right thing.
zett42 wrote:
> Sorry, I just noticed that "FeatureGroup" is already listed as possible
> parent of "MergeRef", where it really belongs to :)
>
>
> zett42 wrote:
>
>> Thank you for this hint. Then there is indeed no need for MergeGroup. It
>> might help to add
Sorry, I just noticed that "FeatureGroup" is already listed as possible
parent of "MergeRef", where it really belongs to :)
zett42 wrote:
>
> Thank you for this hint. Then there is indeed no need for MergeGroup. It
> might help to add "FeatureGroup" to the list of possible parents of the
> "Mer
Thank you for this hint. Then there is indeed no need for MergeGroup. It
might help to add "FeatureGroup" to the list of possible parents of the
"Merge" element in the documentation.
Rob Mensching-6 wrote:
>
> A FeatureGroup doesn't mean there is a Feature contained. A FeatureGroup
> contains
A FeatureGroup doesn't mean there is a Feature contained. A FeatureGroup
contains all of the stuff a Feature can contain. Just define a
FeatureGroup with only MergeRef elements in it.
zett42 wrote:
> Yeah, I could live with it. But it doesn't feel right to create an artificial
> feature just for
Pally Sandher wrote:
> Again what benefits and/or advantages would that have over using a
> Feature with Display="hidden" Level="1" Absent="disallow" set?
>
Why does WiX have any *Group/*GroupRef elements? So the internal
structure of your authoring isn't exposed except as necessary. Features
Disclaimer
-Original Message-
From: zett42 [mailto:sa...@gmx.de]
Sent: 20 May 2009 16:33
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] MergeGroup / MergeGroupRef
Quoting from the Windows Installer documentation:
"A feature is a part of the application's total
d. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
>
>
> -----Original Message-
> From: zett42 [mailto:sa...@gmx.de]
> Sent: 20 May 2009 13:37
> To: wix-users@li
istered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: zett42 [mailto:sa...@gmx.de]
Sent: 20 May 2009 13:37
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] MergeGroup / MergeGroupRef
Yeah, I could live
Yeah, I could live with it. But it doesn't feel right to create an artificial
feature just for grouping merge modules. It is not intuitive for WiX
beginners I think.
Rob Mensching-6 wrote:
>
> Doesn't FeatureGroup/FeatureGroupRef do what you want? It also allows
> Features, but that should be
Doesn't FeatureGroup/FeatureGroupRef do what you want? It also allows
Features, but that should be okay, right?
Bob Arnson wrote:
> zett42 wrote:
>
>> So would it make sense to add new elements "MergeGroup" and "MergeGroupRef"
>>
>>
>
> Sure, feel free to file a feature request.
>
> --
>
zett42 wrote:
> So would it make sense to add new elements "MergeGroup" and "MergeGroupRef"
>
Sure, feel free to file a feature request.
--
sig://boB
http://joyofsetup.com/
--
Crystal Reports - New Free Runtime and
I noticed that it is currently not possible to reference a group of merge
modules (e. g. VC++ runtimes) which are defined in another file, other than
grouping the merge modules in a feature. Than we can use to
reference the merge modules.
So would it make sense to add new elements "MergeGroup" a
12 matches
Mail list logo
