We schedule RemoveExistingProducts after InstallValidate, so it should be
safe to change all component ids.
Are there any issues upgrading 63-bit to 64-bit (as far as Windows Installer
is concerned)?
On Mon, Sep 6, 2010 at 23:34, Rob Mensching wrote:
> If you schedule your RemoveExistingProduct
If you schedule your RemoveExistingProducts early, that removes the previous
version of the product before installing the new one. Essentially that gives
you a clean slate to rev all of your Component GUIDs.
Pretty much all the other options mean you have to be very careful about
managing your Com
I have a few more questions. We have a 32-bit installer today with all
component ids explicitly specified. We are planning to move to 32/64 bit
installer (mutualy exclusive) with the ability to upgrade current
installations (major upgrade).
1. Should we update explicit component ids to "*"?
2. Wha
SHA1 hash of the target path. It took us a long time to come up with it but
we finally got it. You can see the code in wix\src\wix\Binder.cs -
Binder::SetComponentGuids()
On Sun, Sep 5, 2010 at 8:59 AM, Alex Ivanoff wrote:
> > No. "*" component guids are stable, not randomly generated.
>
> If the
> No. "*" component guids are stable, not randomly generated.
If they are stable how are they generated and where the actual values
are stored? Can you explain this?
--
This SF.net Dev2Dev email is sponsored by:
Show off
On 03-Sep-10 01:59, Andres Juarez wrote:
> Ok, so if I use "*" as component GUIDs, this means that small updates are out
> of the questions for this approach, right?
No. "*" component guids are stable, not randomly generated.
> If a 32-bit component is contained in both a 32-bit installation
nt IDs, just as 32- and 64-bit
products should have different product codes.
Or am I reading this wrong?
Thanks
Andres
> Date: Thu, 2 Sep 2010 08:40:48 -0400
> From: b...@joyofsetup.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Newbie x64 msi question
&g
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Newbie x64 msi question
>
> Hi,
> I have recently made a 64 bit MSI from a single source and I started out
> by following
> http://blogs.msdn.com/b/astebner/archive/2007/08/09/4317654.aspx
>
> The trick to ma
On 30-Aug-10 01:36, Andres Juarez wrote:
> So, running candle with teh -arch switch does take care of marking the
> components at 64 bits, but if using the same Wix source file for the
> 32 and 64 bits installer with the only difference of the candle -arh
> switch, the Components GUIDS for the
Do component GUIDs have to be different?
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Tuesday, August 31, 2010 03:54
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Newbie x64 msi question
Hi,
I have recently made a 64 bit MSI from a single source
rez [mailto:andresj_...@hotmail.com]
Sent: 30 August 2010 06:37
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Newbie x64 msi question
Hi Bob,
In your post
> http://www.joyofsetup.com/2010/05/14/working-hard-or-hardly-working/.
> Use the -arch switch and you get smart defaults.
DS per components, I am
almost sure we do, but just asking.
Thanks
Andres
> Date: Sat, 7 Aug 2010 10:56:31 -0400
> From: b...@joyofsetup.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Newbie x64 msi question
>
> On 8/4/2010 9:57 AM, Pally Sandher wrote:
>
On 8/4/2010 9:57 AM, Pally Sandher wrote:
> You need to set the Win64 attribute on your components. If it's not set
> they default to 32-bit components in an x64 package.
> An easy way to do it is to use a pre-processor variable set to "no" or
> "yes" whether you're building x86 or x64 packages res
You need to set the Win64 attribute on your components. If it's not set
they default to 32-bit components in an x64 package.
An easy way to do it is to use a pre-processor variable set to "no" or
"yes" whether you're building x86 or x64 packages respectively. Then you
can simply use something like
14 matches
Mail list logo
