Actually, sounds like a good time to switch to auto-guid.
On Tue, Feb 8, 2011 at 8:02 AM, Quinton Tormanen
wrote:
> Since we don't share these components with any other installers at this
> point, and we only do major updates (no minor updates or patches), would
> there be any harm in us taking t
Since we don't share these components with any other installers at this
point, and we only do major updates (no minor updates or patches), would
there be any harm in us taking this opportunity to switch all 12
component GUIDs to '*'? If there are scenarios where auto-guid isn't
recommended, please
If the Components are mutually exclusive, then you can probably get away
with the same GUIDs. I personally would start planning to get the GUIDs to
be different (auto-guid is ideal) just in case the mutual exclusivity runs
out.
On Mon, Feb 7, 2011 at 11:23 AM, Quinton Tormanen
wrote:
> We've dist
We've distributed our application for some time as a 32-bit app, and
then later we added a 64-bit installer to get the 64-bit USB drivers
installed, but still installed our native application as 32-bit (using
WOW64). Now I need to make the 64-bit installer use the 64-bit EXE
(while the 32-bit insta
Bob,
No, I have not changed the directories. The commands I run are:
heat dir KDS5.0 -gg -o KDS50_1.wxs
heat dir KDS5.0 -gg -o KDS50_2.wxs
-gg means generating guids now. If this is the right one, shall I use:
-ag autogenerate component guids at compile time
Thanks, Shibo
--
View thi
shibo wrote:
> My tests show that directory / component Ids stay the same from
> build-to-build, but not their GUIDs.
>
Do you change directories?
> Does this mean that only directory / component Ids are used in patching in
> WiX 3.0, not GUIDs?
>
No, they all need to be consistent for pat
: [WiX-users] Component GUIDs
>From the Wix documentation:
For the Component element the generated GUID is based on the install
directory and filename of the KeyPath for the component. This GUID will stay
consistent from build-to-build provided the directory and filename of the
KeyPath do not cha
>From the Wix documentation:
For the Component element the generated GUID is based on the install
directory and filename of the KeyPath for the component. This GUID will stay
consistent from build-to-build provided the directory and filename of the
KeyPath do not change.
2009/7/21 shibo
>
> Rob
Rob,
In your reply: "If you generate GUIDs every time you build, you won't be
able to do any upgrades or patching".
We are using WiX 2.0 (planning to upgrade to 3.0). No problem to create
patches given ProductCode and UpgradeCode GUIDs are the same, but with
different components' GUIDs. My unde
: [WiX-users] Component Guids - Version Changes
Laxmi Narsimha Rao Oruganti (SQL CE) wrote:
2)The GUID is pretty much stable (rather same) across all MSI where a
fragment (locale independent) is used. However, I still think that for
performance reasons, the GUID getting generated at compile
Laxmi Narsimha Rao Oruganti (SQL CE) wrote:
*2)*The GUID is pretty much stable (rather same) across all MSI
where a fragment (locale independent) is used. However, I still think
that for performance reasons, the GUID getting generated at compile
time is better. Don't know with whom I ca
Chris Ridd
Sent: Saturday, October 13, 2007 11:07 AM
To: wix-users@lists.sourceforge.net
Cc: SQL Server CE Setup Team
Subject: Re: [WiX-users] Component Guids - Version Changes
On 13 Oct 2007, at 18:53, Laxmi Narsimha Rao Oruganti (SQL CE) wrote:
> 2)The GUID is pretty much stable (rather sa
On 13 Oct 2007, at 18:53, Laxmi Narsimha Rao Oruganti (SQL CE) wrote:
> 2)The GUID is pretty much stable (rather same) across all MSI
> where a fragment (locale independent) is used. However, I still
> think that for performance reasons, the GUID getting generated at
> compile time is be
users@lists.sourceforge.net
Cc: SQL Server CE Setup Team
Subject: RE: [WiX-users] Component Guids - Version Changes
The bit in Derek's article under Here's how it works explains how it works. It
computes the full target path for the single file in the component (multiple
files are not supp
ent: 12 October 2007 08:00
To: wix-users@lists.sourceforge.net
Cc: SQL Server CE Setup Team
Subject: [WiX-users] Component Guids - Version Changes
Hey WIX Users,
I am using WIXv3 3.0.2921 build. And I am able to use automatic
component guid generation as stated by De
Hey WIX Users,
I am using WIXv3 3.0.2921 build. And I am able to use automatic
component guid generation as stated by Derek in:
http://installing.blogspot.com/2006/09/automatically-generating-component.html
I also understand that this is a new feature in WIX
Chris Ridd wrote:
> So I think all we want is the ability to do major upgrades, in which case we
> only need to record the Component GUIDs for shared Components.
>
Well, you can't ignore them entirely; they're useful during debugging,
for example. But that's easy enough to do with a version-co
Stefan Krueger posted recently in the psdk group:
"Also with MSI 4.5 you can embed the launcher in the .msi file, eliminationg
the need for an external exe, and improving compatibility with deployment
via Active Directory. "
I wonder if this raises the possibility of addressing issues li
On 5/9/07 4:49, "Bob Arnson" <[EMAIL PROTECTED]> wrote:
> Chris Ridd wrote:
>> How are Component GUIDs used by the installer during (say) a package
>> upgrade, or at other times? Do *I* need to remember the GUIDs for all the
>> Components I'm installing?
>>
>
> If you generate GUIDs every time
Chris Ridd wrote:
> I'm having some conceptual problems with WIX's s though, in
> particular their GUID attributes. Curiously (for us) Installshield makes
> *way* less use of GUIDs than WIX, so my practical problem is how to manage
> the $large_number of GUIDs that will be required. Oh yes, 2 * $la
Hi,
I'm in the process of altering our Windows package building scripts from
using Installshield to using WIX. So far (cross fingers) so good.
I'm having some conceptual problems with WIX's s though, in
particular their GUID attributes. Curiously (for us) Installshield makes
*way* less use of GUI
21 matches
Mail list logo
