users@lists.sourceforge.net
Subject: Re: [WiX-users] Using heat.exe as part of an automated build process
The problem here is that Microsoft tools are already in the habit of automatic
code generation - and they all are designed to produce code for SELF
REGISTRATION. The process of self registrati
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dyson,
Peter
Sent: 21 May 2007 10:58
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using heat.exe as part of an automated build
Although Rob et al, don't recommend this approach we have
NG-CON) [mailto:[EMAIL PROTECTED]
Sent: Monday, May 21, 2007 12:21 PM
To: Rob Mensching; Scott Palmer
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Using heat.exe as part of an automated build process
Thanks Rob. But the "code divination" that you speak of is not really what
AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using heat.exe as part of an automated build process
Thanks for the heads up. I'll bear that in mind.
Presumably, changing the root folder for the files each time would solve
this problem then.
so
sample-v1
sample-v2, etc woul
Well said, Dacian.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of fiordean dacian
Sent: Wednesday, May 23, 2007 2:00 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using heat.exe as part of an automated build process
Scott,
Not everything that goes into the
y, May 22, 2007 8:34 PM
To: Scott Palmer
Cc: Rob Mensching; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using heat.exe as part of an automated build
process
Scott Palmer wrote:
Anyway... I'm just looking for a build process, including creating the
installer, that doesn
Palmer <[EMAIL PROTECTED]>
To: Rob Mensching <[EMAIL PROTECTED]>
Cc: "wix-users@lists.sourceforge.net"
Sent: Tuesday, May 22, 2007 10:08:59 PM
Subject: Re: [WiX-users] Using heat.exe as part of an automated build process
The problem here is that Microsoft tools are already in th
Scott Palmer wrote:
Anyway... I'm just looking for a build process, including creating the
installer, that doesn't suck...
Just FYI: Saying that something "sucks" is neither useful nor constructive.
--
sig://boB
http://joyofsetup.com/
--
The problem here is that Microsoft tools are already in the habit of
automatic code generation - and they all are designed to produce code for
SELF REGISTRATION. The process of self registration is effectively
encouraged by the development environment.
Now if the development process has to chang
ot; <[EMAIL PROTECTED]>
>>Subject: Re: [WiX-users] Using heat.exe as part of an automated build
>> process
>>To: "Rob Mensching" <[EMAIL PROTECTED]>, "Scott Palmer"
>> <[EMAIL PROTECTED]>
>>Cc: wix-users@lis
One of the teams in our company has it's own script for creating the WiX
fragment for a large set of
files. It doesn't use heat or tallow, it creates everything itself. The start
of the file is
always the same, as is the end. It's only the XML under the top directory that
ever changes. The
After receiving emails from people on this subject asking about our
process, I will reply to all publicly here.
Unfortunatly my employer 'owns' the code, getting OS in the door is hard
enough, getting it out is not an option I am afraid.
However for those interested the general methodology used
From: "Mike Dimmick" <[EMAIL PROTECTED]>
To: "'Anthony Wieser'" <[EMAIL PROTECTED]>;
Sent: Tuesday, May 22, 2007 12:17 AM
Subject: RE: [WiX-users] Using heat.exe as part of an automated build
process
> Yes, you're breaking rule 1 of the component
e.net
Subject: Re: [WiX-users] Using heat.exe as part of an automated build
Although Rob et al, don't recommend this approach we have been using
Heat, and it's predecessor, as part of our automated build process for
over a year with Wix3.
The main things to be wary of are the spurious entri
27;s each time I do an
update, apart from installation speed?
Anthony Wieser
Wieser Software ltd
- Original Message -
From: Yexley, Robert (LNG-CON)
To: Rob Mensching ; Scott Palmer
Cc: wix-users@lists.sourceforge.net
Sent: Monday, May 21, 2007 8:21 PM
Subject: Re: [WiX-users] Using heat.exe
Systems Limited
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Anthony
Wieser
Sent: 21 May 2007 20:46
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using heat.exe as part of an automated build
process
I've just bu
ny Wieser
Wieser Software ltd
- Original Message -
From: Yexley, Robert (LNG-CON)
To: Rob Mensching ; Scott Palmer
Cc: wix-users@lists.sourceforge.net
Sent: Monday, May 21, 2007 8:21 PM
Subject: Re: [WiX-users] Using heat.exe as part of an automated build
process
Thanks Rob. But the &
// YEX //
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Monday, May 21, 2007 1:16 PM
To: Yexley, Robert (LNG-CON); Scott Palmer
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Using heat.exe as part of an automated
ered at Hogwarts
yet.
From: Yexley, Robert (LNG-CON) [mailto:[EMAIL PROTECTED]
Sent: Monday, May 21, 2007 6:19 AM
To: Rob Mensching; Scott Palmer
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Using heat.exe as part of an automated build process
Is WiX designed to be used in an au
Yexley, Robert (LNG-CON) wrote:
Is WiX designed to be used in an automated build process?
The WiX tools, of course. The subject of this thread is your setup
*authoring*.
The code based that it needs to be generated from is a moving
target...changes on a ~weekly basis.
Because the WiX tool
Palmer
Sent: Monday, May 21, 2007 9:49 AM
To: Rob Mensching
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using heat.exe as part of an automated build
process
But it obviously should be. I hope this can be fixed, since we are
stuck with having to deal with all the problems of CO
But it obviously should be. I hope this can be fixed, since we are stuck
with having to deal with all the problems of COM and for some silly reason
(I haven't seen a good argument against it yet) SelfReg is not supported and
officially broken for dynamically linked DLLs on Vista.
Microsoft also
Yexley, Robert (LNG-CON)
Cc: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Using heat.exe as part of an automated build
process
Heat isn't designed to be used in an automated build process.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott
Palmer
Sent: Frida
Although Rob et al, don't recommend this approach we have been using
Heat, and it's predecessor, as part of our automated build process for
over a year with Wix3.
The main things to be wary of are the spurious entries generated by
Heat, for example VB6 entries which should not be there.
However t
Heat isn’t designed to be used in an automated build process.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Palmer
Sent: Friday, May 18, 2007 7:10 PM
To: Yexley, Robert (LNG-CON)
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Using heat.exe as part of an
Not exactly. If you use Heat on a COM DLL, Heat inserts "PUT-GUID-HERE" for
the GUID so you can do a search/replace as part of the automated build to
keep the GUID correct and always the same for that component.
Other issues are with the directory structure that Heat uses and the fact
that it's
I'm still learning the ins and outs of WiX. I'm working on trying to
integrate the generation of an MSI into our automated build process, and
was wondering about the possibility of using heat.ext to harvest the
files needed for the features and components for the MSI. I've read a
few archived messa
27 matches
Mail list logo
