-users] Best Practices - Using * for GUID
automation
Could someone chime in with a time when you wouldn't want to use *
on
component Guids? Would this cause issues with generating patches?
-James
On Tue, Jun 29, 2010 at 1:19 PM, Andy Clugston clug...@gmail.com
wrote
This is the expected behavior for that configuration. The problem is that
since your component GUIDs don't line up from v1.0.0 to v1.0.1 the upgrade
installs the new components and then after InstallFinalize removes the old
components because it is not able to properly reference count them using
Hi Mike,
Thanks for the info. What you stated is what I am seeing in the verbose
logs. I see where the files are being copied, and then I see where they are
being removed. Doing a diff between the good v1.0.0 case and the bad
v1.0.0 case makes it obvious.
So if I understand you on the
Hi Andy,
Either setting After=InstallValidate or Before=InstallInitialize will
work, you don't need to specify both. I was just giving you the
restrictions on sequencing for the upgrade to work.
With this setup a rollback to v1.0.0 would not occur if your v1.0.1 MSI
fails after
-users] Best Practices - Using * for GUID automation
Mike,
Thanks again for the reply.
I have added RemoveExistingProducts Before=InstallInitialize/ and it
works as you stated. Actually, WiX disallows both After and Before in
the same element.
I understand the rollback scenario now as well
Andy,
If you have a RemoveExistingProducts action scheduled in one location in
your common element and another scheduled elsewhere in your Product
consuming the common WiX I'm pretty sure you would get a compilation error.
You could set something up in your common WiX fragments/include to
...@slowcommotion.com]
Sent: Tuesday, June 29, 2010 11:06 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Best Practices - Using * for GUID automation
Could someone chime in with a time when you wouldn't want to use * on
component Guids? Would
I am trying to determine the best approach to take with creating GUIDs for
the various WiX elements. We use a full upgrade approach so I believe for
the Product Id=* is okay. It probably goes without saying that setting
Package Id=* makes sense in all cases. It is my understanding that the
: [WiX-users] Best Practices - Using * for GUID automation
I am trying to determine the best approach to take with creating GUIDs
for the various WiX elements. We use a full upgrade approach so I
believe for the Product Id=* is okay. It probably goes without saying
that setting Package Id=* makes
-Original Message-
From: Andy Clugston [mailto:clug...@gmail.com]
Sent: Tuesday, June 29, 2010 7:35 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Best Practices - Using * for GUID automation
I am trying to determine the best approach to take with creating
]
Sent: Tuesday, June 29, 2010 7:35 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Best Practices - Using * for GUID automation
I am trying to determine the best approach to take with creating GUIDs
for the various WiX elements. We use a full upgrade
.
Subject: Re: [WiX-users] Best Practices - Using * for GUID automation
Could someone chime in with a time when you wouldn't want to use * on
component Guids? Would this cause issues with generating patches?
-James
On Tue, Jun 29, 2010 at 1:19 PM, Andy Clugston clug...@gmail.com wrote:
Okay
using guids that were not *?
-Original Message-
From: James Poole [mailto:w...@slowcommotion.com]
Sent: Tuesday, June 29, 2010 11:06 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Best Practices - Using * for GUID automation
Could someone chime
.
Subject: Re: [WiX-users] Best Practices - Using * for GUID automation
Could someone chime in with a time when you wouldn't want to use * on
component Guids? Would this cause issues with generating patches?
-James
On Tue, Jun 29, 2010 at 1:19 PM, Andy Clugston clug...@gmail.com
wrote
14 matches
Mail list logo
