r 28, 2011 6:52 AM
To: "General discussion for Windows Installer XML toolset."
Subject: Re: [WiX-users] GUID vs. * for components (Was: RE:
WiX-usersDigest, Vol 64, Issue 49)
This may clear up your confusion.
The * guid is generated based on the path in the installer at build time
unresolved paths are the same.
-Original Message-
From: Christopher Painter [mailto:chr...@iswix.com]
Sent: 28 September 2011 12:22
To: Rob Mensching; General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] GUID vs. * for components (Was: RE: WiX-usersDigest,
Vol 64
;
Sent: Tuesday, September 27, 2011 11:30 PM
To: chr...@iswix.com, "General discussion for Windows Installer XML
toolset."
Subject: Re: [WiX-users] GUID vs. * for components (Was: RE: WiX-users
Digest, Vol 64, Issue 49)
AFAIK, merge modules aren't treated differently from MSIs wrt
---
>
> From: "Rob Mensching"
>
> Sent: Tuesday, September 27, 2011 8:01 AM
>
> To: "General discussion for Windows Installer XML toolset."
>
>
> Subject: Re: [WiX-users] GUID vs. * for components (Was: RE: WiX-use
]
Sendt: 27. september 2011 14:50
Til: General discussion for Windows Installer XML toolset.
Emne: Re: [WiX-users] GUID vs. * for components (Was: RE: WiX-users Digest,
Vol 64, Issue 49)
Well, my opinion is my opinion. People are welcome to disagree with my
opinion
For example, a few people around
mponent ID
paradigm as the absolute path to the keypath is never truly absolute.
Chris
From: "Rob Mensching"
Sent: Tuesday, September 27, 2011 8:01 AM
To: "General discussion for Windows Installer XML toolset."
Subject:
Well, my opinion is my opinion. People are welcome to disagree with my
opinion
For example, a few people around here (including some clients) disagree with
me whether MajorUpgrade/@AllowSameVersionUpgrades is a "good thing" or not.
It's only when something *really* doesn't work and people want t
And I would think your opinion carries at least SOME weight on the issue *grin*
A follow up question though, I have a hard time understanding the difference of
the two.
All the documentation is a bit on thin side, or I do simply not understand the
issue.
So, to refrase, what are the advantage
Thanks! That certainly is easier.
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Friday, April 01, 2011 10:43 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Guid for COM components
Wix will generate a component guid
rgman [mailto:john.berg...@xpedienttechnologies.com]
Sent: 01 April 2011 16:25
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Guid for COM components
Can someone explain why this is the preferred practice?
-Original Message-
From: Peter Shirtc
Can someone explain why this is the preferred practice?
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Friday, April 01, 2011 9:59 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Guid for COM components
The preferred
The preferred practice is to use * as the component GUID whether it is COM or
not.
-Original Message-
From: swapna.rachako...@thomsonreuters.com
[mailto:swapna.rachako...@thomsonreuters.com]
Sent: 01 April 2011 15:51
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Guid for COM
Hello experts
Could anyone help me in
How to provide Guid's for COM Components ??
Thanks in advance
Swapna
--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code y
ows Installer XML toolset.
Subject: Re: [WiX-users] GUID Autogen question
Tried the example you supplied. Same results, same error. Following is
new snippet:
Thanks,
Bob
Error Text:
ICE0
, 2010 12:54 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] GUID Autogen question
I have seen this before and I think it is because you have a period in
the component name, try simply using this syntax:
You component id will then be the
December 2010 17:25
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] GUID Autogen question
I'm using the snippet below to define components. I'm attempting to use
the GUID="*" (Autogen ) on the components. However, on each of the
component statments I am getting an ICE
I'm using the snippet below to define components. I'm attempting to use the
GUID="*" (Autogen ) on the components. However, on each of the component
statments I am getting an ICE08 Component ... has a duplicate GUID. The GUID
value in the error message is the same for all 3 errors (component
Ohh, I completely understand the many possible uses, but that sounds
more like an app configuration problem than something that WiX is
geared towards. I'm just a proponent of picking the right tool for
the job, and in this case WiX isn't the best tool for the job, a CA
is... IMHO.
On Mon, Jul 28,
In article <[EMAIL PROTECTED]>,
"Erik Garcia" <[EMAIL PROTECTED]> writes:
> Pardon my french, but why the frak would you want to do something
> nondeterministic in a setup/installation package?
Perhaps you want to uniquely identify each install for bug reporting
purposes.
--
"The Direct3D
om: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns
Sent: Monday, July 28, 2008 07:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] GUID generation in WiX
That GUID would be generated at MSI build time, not at MSI install time, so it
won't be
l discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] GUID generation in WiX
>
> You could try something like
>
>
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stas
> Klyachkovsky
> Sent: 28 Ju
ssion for Windows Installer XML toolset.
Subject: Re: [WiX-users] GUID generation in WiX
You could try something like
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stas Klyachkovsky
Sent: 28 July 2008 12:32
To: wix-users@lists.sourceforge.net
Subject:
You could try something like
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stas Klyachkovsky
Sent: 28 July 2008 12:32
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] GUID generation in WiX
Hi there,
I need to generate a GUID during the
Hi there,
I need to generate a GUID during the setup and put it in the registry key.
Is there a simple way to generate random GUID in Windows Installer during
installation? Is there WiX tag to do this?
Thanks,
Stas
-
This SF.
-users@lists.sourceforge.net
Subject: [WiX-users] GUID for different platforms
The project is a driver that supports x86 and amd64 platforms.
Do I need to create new wxs-file with its own unique GUIDs for ,
and , or can I use the same wxs-file
for all platforms?
In the latter case msi-packages will
The project is a driver that supports x86 and amd64 platforms.
Do I need to create new wxs-file with its own unique GUIDs for ,
and , or can I use the same wxs-file
for all platforms?
In the latter case msi-packages will be different by (there is
auto creation for in wxs:
'--???
Jesper Hogstrom wrote:
To the best of my understanding there is no wix-macro that descends a
folder structure and grabs everything it finds. Is that correct?
Yes.
How important is it to keep GUIDs stable over time for components? Is
the better solution to get to it and simply specify all file
If by "descends a folder structure and..." you mean you want something that
will generate the WiX code for you, then yes. There is heat.exe that comes
with WiX version 3.
On 2/5/07, Jesper Hogstrom <[EMAIL PROTECTED]> wrote:
I have set up a wix script for most of what I need. However, the
re
I have set up a wix script for most of what I need. However, the
remaining section is a subtree where every single file should be
included - and files may be added every now and then. The file structure
contains demo files.
An obvious solution is to write wix code to specify all files.
Another
ent: 04 October 2006 08:39
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Guid="*"
I am trying out the new feature Guid="*" as described on
http://installing.blogspot.com/2006/09/automatically-generating-component.html
I got some questions:
In the blog beta-testers are
I am trying out the new feature Guid="*" as described on
http://installing.blogspot.com/2006/09/automatically-generating-component.html
I got some questions:
In the blog beta-testers are encouraged to try it out:
When using it a warning is shown, that this is experimental.
Among others it claims t
31 matches
Mail list logo
