Thanks, Rob,
yes, referring to the Module Guid works!
Thanks,
Stephan.
On Wed, May 20, 2009 at 2:18 AM, Rob Mensching wrote:
> I assume you mean setting the Module Id through the Package/@Id
> attribute *does* work, right?
>
> stephan o'farrill wrote:
>> Thanks Rob,
>>
>> I just needed to be c
I assume you mean setting the Module Id through the Package/@Id
attribute *does* work, right?
stephan o'farrill wrote:
> Thanks Rob,
>
> I just needed to be convinced again to keep trying (after I thought I
> was through all possible combinations):
> Now I replaced "-" with "_" in the GUIDs and v
Thanks Rob,
I just needed to be convinced again to keep trying (after I thought I
was through all possible combinations):
Now I replaced "-" with "_" in the GUIDs and viola!
BTW. having a Guid attribute in a Module element is deprecated in WiX3
- using the Guid from the Package instead does not w
You'd have to refer to the Directory/@Id (that is in ALL CAPS, of
course) with the Module GUID attached as well.
stephan o'farrill wrote:
> Hi,
> Is it possible to select the install path (with UI) for one of the
> directories in a merge module (containing several directories) from
> the enclosin
Hi,
Is it possible to select the install path (with UI) for one of the
directories in a merge module (containing several directories) from
the enclosing WiX3 product installer script?
If yes, how do I have to define the property outside the merge module
to be able to reference it inside the referri
5 matches
Mail list logo