To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Heat and GUIDs
Thanks Blair, I think that answers my question.
What you are saying implies that there is no random component to the
GUID generation, So it is not randomly generated (as is the case with
standard gui
luding the hash methodology) is supposed to be stable without
> any box-to-box differences.
>
> -Original Message-
> From: little.forest [mailto:little.for...@ymail.com]
> Sent: Tuesday, October 20, 2009 4:20 PM
> To: General discussion for Windows Installer XML toolset.
s.
-Original Message-
From: little.forest [mailto:little.for...@ymail.com]
Sent: Tuesday, October 20, 2009 4:20 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Heat and GUIDs
I also run into a GUID and "*" related issue:
I have all of the c
General discussion for Windows Installer XML toolset.
Sent: Tuesday, October 20, 2009 4:05:13 PM
Subject: Re: [WiX-users] Heat and GUIDs
the help about -ag says: "autogenerate component guids at compile time"
I assumed this would mean that each time it is compiled a new guid was
gene
the help about -ag says: "autogenerate component guids at compile time"
I assumed this would mean that each time it is compiled a new guid was
generated.
If in fact the guid is static as you say, it must be recorded somewhere
(all the file has in it is "*"), ie wix would have to know what guid
Hey Daniel,
Are you sure you are getting NEW GUIDs when using the "*" (-ag switch in
heat.exe)? These should actually be static.
Thanks,
Brian Rogers
"Intelligence removes complexity." - Me
http://blogs.msdn.com/icumove <-- NEW
On Tue, Oct 20, 2009 at 2:47 PM, Daniel Hughes wrote:
> If I use
If I use heat to harvest the contents of a folder, I can set it to
either generated GUIDs then or at compile time, or by default to put in
place holders.
However if I set it to generate GUIDs then, I will get a different GUID
each time I run HEAT.
If I set it to generate GUIDs at compile time
7 matches
Mail list logo
