"Mike Dimmick" <[EMAIL PROTECTED]> writes:
> If I understand correctly, I believe Bob is saying that the
> component GUIDs in your installer should also be stable, which
> cannot currently be achieved with tallow.
Yes, but tallow (used with option -reg) does not generate
elements at all. All it
: Mike Dimmick; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using a generated (by tallow.exe) fragment file in
acomponent
Bob Arnson <[EMAIL PROTECTED]> writes:
> Jarl Friis wrote:
>> appropriate element). I have expected to be able to avoid
>> that for the standard reasons:
Bob Arnson <[EMAIL PROTECTED]> writes:
> Jarl Friis wrote:
>> appropriate element). I have expected to be able to avoid
>> that for the standard reasons:
>> It's time consuming.
>> It does not require intelligence.
>> It's error prone; In half-a-year, when I actually do make an
>>
> Problem is: I
Jarl Friis wrote:
> appropriate element). I have expected to be able to avoid
> that for the standard reasons:
> It's time consuming.
> It does not require intelligence.
> It's error prone; In half-a-year, when I actually do make an
>
Problem is: It does require intelligence. See, for example:
Hi Mike.
Thanks for the detailed answer (though it seems to drift off-topic).
"Mike Dimmick" <[EMAIL PROTECTED]> writes:
> Copy and paste into a .wxs file that describes your component,
> underneath the appropriate element. Tallow is not
> intended for use in automated build processes.
:-(
>
users@lists.sourceforge.net
Subject: [WiX-users] Using a generated (by tallow.exe) fragment file in
acomponent
Hi.
I have started a versy small project (very close to SampleFirst.ZIP).
However The build procedure is this:
regasme.exe /regfile MyAssembly.dll generates a MyAssembly.reg file.
The regfile is
6 matches
Mail list logo
