Re: [WiX-users] Force overwrite DLL with previous version inMajorUpgrade?
Putting REP before CostInitialize has the desired effect - you still
see the warning about disallowing the install because a higher version
exists, but the l.ower versioned file ends up on the system.
It seems to be a bug that with REP after (say) InstallValidate it
refuses to install the file. What I see is that the file is not
installed at all, which is the first sign of a bug, and secondly if
you do a repair it does install the lower version of the file.
---
Phil Wilson
On Wed, Nov 26, 2014 at 1:49 PM, Joel Budreau joel.budr...@gmail.com wrote:
Hey Phil,
Can you tell me how it’s possible to schedule RemoveExistingProducts early
enough to avoid versioning rules being applied? I’m under the impression that
versioning rules are applied during CostFinalize, which has to come before
InstallInitialize, which has to come before RemoveExistingProducts. Am I
missing something?
Thanks,
Joel
On Nov 26, 2014, at 2:39 PM, Phil Wilson phildgwil...@gmail.com wrote:
It's an anomaly or the same bug in non SxS situations. It's not an
installer limitation because an REP early in the install will remove
the older product before the new one regardless of versions. You
haven't posted your upgrade or majorupgrade WiX source, so it's worth
verifying that you are really doing a major upgrade and that
RemoveExistingProducts is in the appropriate place. If it's after
InstallExecute then it's at the end and that will definitely invoke
file versioning rules. Not all major upgrades are the same and you
must have REP early to avoid versioning rules being applied.
---
Phil Wilson
On Tue, Nov 25, 2014 at 1:24 PM, Joel Budreau joel.budr...@gmail.com wrote:
Hey Klaus,
If you want to perform a major upgrade and make sure all the files from the
newer installer are copied, make use of the REINSTALLMODE property -
http://msdn.microsoft.com/en-us/library/aa371182%28v=vs.85%29.aspx If you
set REINSTALLMODE=amus, the ‘a’ will ensure that all the new files are
installed (regardless of the versions that are already installed).
Joel
On Nov 25, 2014, at 2:06 AM, Klaus Gütter klaus.guet...@it-gmbh.de wrote:
Hi Phil,
thank you for the KB link. But this situation does not apply to our case
(no GAC or SxS involved).
From the verbose log, I see that already in CostFinalize, the installer
decides not to install the component:
MSI (s) (BC:C8) [10:46:51:830]: Disallowing installation of component:
{5572161F-6A73-4552-91C7-8108C28DF8CE} since the same component with
higher versioned keyfile exists.
RemoveRelatedProduct does however happily remove the component.
Looks like an Installer limitation.
Klaus Gütter
-Ursprüngliche Nachricht-
Von: Phil Wilson [mailto:phildgwil...@gmail.com]
Gesendet: Montag, 24. November 2014 21:34
An: General discussion about the WiX toolset.
Betreff: Re: [WiX-users] Force overwrite DLL with previous version
inMajorUpgrade?
After InstallValidate should definitely work for a major upgrade. If that
2.4 version is not installed then you may have that MSI bug, especially if
the file is in the GAC or SxS
http://support.microsoft.com/kb/905238 and see if a repair restores the
file.
Anyway, take a verbose log and search for the file name and its component
id. There are more routine possible issues, such as the component id being
inadvertently shared with something, and hopefully the Dll is marked as
key path.
---
Phil Wilson
On Mon, Nov 24, 2014 at 3:39 AM, Klaus Gütter klaus.guet...@it-gmbh.de
wrote:
Hello,
I have the following situation: MyProduct version 1.1 uses ThirdPartyDll
version 2.5. For MyProduct version 1.2 we had to go back to ThirdPartyDll
version 2.4.
Is it possible to use an Major Upgrade in this situation? I had no luck
with this up to now:
- when scheduled afterInstallExecute, ThirdPartyDll version 2.5 is not
overwritten (as expected by the Installer rules)
- when scheduled afterInstallValidate, ThirdPartyDll version 2.5 is
removed, but version 2.4 is not installed.
If it matters: the MyProduct 1.1 setup was created with WiX 3.8, version
1.2 with WiX 3.9.
Klaus Gütter
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT
Server from Actuate! Instantly Supercharge Your Business Reports and
Dashboards with Interactivity, Sharing, Native Excel Exports, App
Integration more Get technology previously reserved for
billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.
clktrk ___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from
Actuate! Instantly Supercharge
Re: [WiX-users] Force overwrite DLL with previous version inMajorUpgrade?
It's an anomaly or the same bug in non SxS situations. It's not an
installer limitation because an REP early in the install will remove
the older product before the new one regardless of versions. You
haven't posted your upgrade or majorupgrade WiX source, so it's worth
verifying that you are really doing a major upgrade and that
RemoveExistingProducts is in the appropriate place. If it's after
InstallExecute then it's at the end and that will definitely invoke
file versioning rules. Not all major upgrades are the same and you
must have REP early to avoid versioning rules being applied.
---
Phil Wilson
On Tue, Nov 25, 2014 at 1:24 PM, Joel Budreau joel.budr...@gmail.com wrote:
Hey Klaus,
If you want to perform a major upgrade and make sure all the files from the
newer installer are copied, make use of the REINSTALLMODE property -
http://msdn.microsoft.com/en-us/library/aa371182%28v=vs.85%29.aspx If you set
REINSTALLMODE=amus, the ‘a’ will ensure that all the new files are installed
(regardless of the versions that are already installed).
Joel
On Nov 25, 2014, at 2:06 AM, Klaus Gütter klaus.guet...@it-gmbh.de wrote:
Hi Phil,
thank you for the KB link. But this situation does not apply to our case (no
GAC or SxS involved).
From the verbose log, I see that already in CostFinalize, the installer
decides not to install the component:
MSI (s) (BC:C8) [10:46:51:830]: Disallowing installation of component:
{5572161F-6A73-4552-91C7-8108C28DF8CE} since the same component with higher
versioned keyfile exists.
RemoveRelatedProduct does however happily remove the component.
Looks like an Installer limitation.
Klaus Gütter
-Ursprüngliche Nachricht-
Von: Phil Wilson [mailto:phildgwil...@gmail.com]
Gesendet: Montag, 24. November 2014 21:34
An: General discussion about the WiX toolset.
Betreff: Re: [WiX-users] Force overwrite DLL with previous version
inMajorUpgrade?
After InstallValidate should definitely work for a major upgrade. If that
2.4 version is not installed then you may have that MSI bug, especially if
the file is in the GAC or SxS
http://support.microsoft.com/kb/905238 and see if a repair restores the
file.
Anyway, take a verbose log and search for the file name and its component
id. There are more routine possible issues, such as the component id being
inadvertently shared with something, and hopefully the Dll is marked as key
path.
---
Phil Wilson
On Mon, Nov 24, 2014 at 3:39 AM, Klaus Gütter klaus.guet...@it-gmbh.de
wrote:
Hello,
I have the following situation: MyProduct version 1.1 uses ThirdPartyDll
version 2.5. For MyProduct version 1.2 we had to go back to ThirdPartyDll
version 2.4.
Is it possible to use an Major Upgrade in this situation? I had no luck
with this up to now:
- when scheduled afterInstallExecute, ThirdPartyDll version 2.5 is not
overwritten (as expected by the Installer rules)
- when scheduled afterInstallValidate, ThirdPartyDll version 2.5 is
removed, but version 2.4 is not installed.
If it matters: the MyProduct 1.1 setup was created with WiX 3.8, version
1.2 with WiX 3.9.
Klaus Gütter
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT
Server from Actuate! Instantly Supercharge Your Business Reports and
Dashboards with Interactivity, Sharing, Native Excel Exports, App
Integration more Get technology previously reserved for
billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.
clktrk ___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from
Actuate! Instantly Supercharge Your Business Reports and Dashboards with
Interactivity, Sharing, Native Excel Exports, App Integration more Get
technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists
Re: [WiX-users] Force overwrite DLL with previous version inMajorUpgrade?
Hey Phil,
Can you tell me how it’s possible to schedule RemoveExistingProducts early
enough to avoid versioning rules being applied? I’m under the impression that
versioning rules are applied during CostFinalize, which has to come before
InstallInitialize, which has to come before RemoveExistingProducts. Am I
missing something?
Thanks,
Joel
On Nov 26, 2014, at 2:39 PM, Phil Wilson phildgwil...@gmail.com wrote:
It's an anomaly or the same bug in non SxS situations. It's not an
installer limitation because an REP early in the install will remove
the older product before the new one regardless of versions. You
haven't posted your upgrade or majorupgrade WiX source, so it's worth
verifying that you are really doing a major upgrade and that
RemoveExistingProducts is in the appropriate place. If it's after
InstallExecute then it's at the end and that will definitely invoke
file versioning rules. Not all major upgrades are the same and you
must have REP early to avoid versioning rules being applied.
---
Phil Wilson
On Tue, Nov 25, 2014 at 1:24 PM, Joel Budreau joel.budr...@gmail.com wrote:
Hey Klaus,
If you want to perform a major upgrade and make sure all the files from the
newer installer are copied, make use of the REINSTALLMODE property -
http://msdn.microsoft.com/en-us/library/aa371182%28v=vs.85%29.aspx If you
set REINSTALLMODE=amus, the ‘a’ will ensure that all the new files are
installed (regardless of the versions that are already installed).
Joel
On Nov 25, 2014, at 2:06 AM, Klaus Gütter klaus.guet...@it-gmbh.de wrote:
Hi Phil,
thank you for the KB link. But this situation does not apply to our case
(no GAC or SxS involved).
From the verbose log, I see that already in CostFinalize, the installer
decides not to install the component:
MSI (s) (BC:C8) [10:46:51:830]: Disallowing installation of component:
{5572161F-6A73-4552-91C7-8108C28DF8CE} since the same component with higher
versioned keyfile exists.
RemoveRelatedProduct does however happily remove the component.
Looks like an Installer limitation.
Klaus Gütter
-Ursprüngliche Nachricht-
Von: Phil Wilson [mailto:phildgwil...@gmail.com]
Gesendet: Montag, 24. November 2014 21:34
An: General discussion about the WiX toolset.
Betreff: Re: [WiX-users] Force overwrite DLL with previous version
inMajorUpgrade?
After InstallValidate should definitely work for a major upgrade. If that
2.4 version is not installed then you may have that MSI bug, especially if
the file is in the GAC or SxS
http://support.microsoft.com/kb/905238 and see if a repair restores the
file.
Anyway, take a verbose log and search for the file name and its component
id. There are more routine possible issues, such as the component id being
inadvertently shared with something, and hopefully the Dll is marked as key
path.
---
Phil Wilson
On Mon, Nov 24, 2014 at 3:39 AM, Klaus Gütter klaus.guet...@it-gmbh.de
wrote:
Hello,
I have the following situation: MyProduct version 1.1 uses ThirdPartyDll
version 2.5. For MyProduct version 1.2 we had to go back to ThirdPartyDll
version 2.4.
Is it possible to use an Major Upgrade in this situation? I had no luck
with this up to now:
- when scheduled afterInstallExecute, ThirdPartyDll version 2.5 is not
overwritten (as expected by the Installer rules)
- when scheduled afterInstallValidate, ThirdPartyDll version 2.5 is
removed, but version 2.4 is not installed.
If it matters: the MyProduct 1.1 setup was created with WiX 3.8, version
1.2 with WiX 3.9.
Klaus Gütter
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT
Server from Actuate! Instantly Supercharge Your Business Reports and
Dashboards with Interactivity, Sharing, Native Excel Exports, App
Integration more Get technology previously reserved for
billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.
clktrk ___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from
Actuate! Instantly Supercharge Your Business Reports and Dashboards with
Interactivity, Sharing, Native Excel Exports, App Integration more Get
technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Download BIRT iHub F-Type - The Free Enterprise
Re: [WiX-users] Force overwrite DLL with previous version inMajorUpgrade?
Hey Klaus,
If you want to perform a major upgrade and make sure all the files from the
newer installer are copied, make use of the REINSTALLMODE property -
http://msdn.microsoft.com/en-us/library/aa371182%28v=vs.85%29.aspx If you set
REINSTALLMODE=amus, the ‘a’ will ensure that all the new files are installed
(regardless of the versions that are already installed).
Joel
On Nov 25, 2014, at 2:06 AM, Klaus Gütter klaus.guet...@it-gmbh.de wrote:
Hi Phil,
thank you for the KB link. But this situation does not apply to our case (no
GAC or SxS involved).
From the verbose log, I see that already in CostFinalize, the installer
decides not to install the component:
MSI (s) (BC:C8) [10:46:51:830]: Disallowing installation of component:
{5572161F-6A73-4552-91C7-8108C28DF8CE} since the same component with higher
versioned keyfile exists.
RemoveRelatedProduct does however happily remove the component.
Looks like an Installer limitation.
Klaus Gütter
-Ursprüngliche Nachricht-
Von: Phil Wilson [mailto:phildgwil...@gmail.com]
Gesendet: Montag, 24. November 2014 21:34
An: General discussion about the WiX toolset.
Betreff: Re: [WiX-users] Force overwrite DLL with previous version
inMajorUpgrade?
After InstallValidate should definitely work for a major upgrade. If that
2.4 version is not installed then you may have that MSI bug, especially if
the file is in the GAC or SxS
http://support.microsoft.com/kb/905238 and see if a repair restores the file.
Anyway, take a verbose log and search for the file name and its component id.
There are more routine possible issues, such as the component id being
inadvertently shared with something, and hopefully the Dll is marked as key
path.
---
Phil Wilson
On Mon, Nov 24, 2014 at 3:39 AM, Klaus Gütter klaus.guet...@it-gmbh.de
wrote:
Hello,
I have the following situation: MyProduct version 1.1 uses ThirdPartyDll
version 2.5. For MyProduct version 1.2 we had to go back to ThirdPartyDll
version 2.4.
Is it possible to use an Major Upgrade in this situation? I had no luck with
this up to now:
- when scheduled afterInstallExecute, ThirdPartyDll version 2.5 is not
overwritten (as expected by the Installer rules)
- when scheduled afterInstallValidate, ThirdPartyDll version 2.5 is removed,
but version 2.4 is not installed.
If it matters: the MyProduct 1.1 setup was created with WiX 3.8, version 1.2
with WiX 3.9.
Klaus Gütter
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT
Server from Actuate! Instantly Supercharge Your Business Reports and
Dashboards with Interactivity, Sharing, Native Excel Exports, App
Integration more Get technology previously reserved for
billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.
clktrk ___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from
Actuate! Instantly Supercharge Your Business Reports and Dashboards with
Interactivity, Sharing, Native Excel Exports, App Integration more Get
technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Force overwrite DLL with previous version inMajorUpgrade?
Hi Phil,
thank you for the KB link. But this situation does not apply to our case (no
GAC or SxS involved).
From the verbose log, I see that already in CostFinalize, the installer decides
not to install the component:
MSI (s) (BC:C8) [10:46:51:830]: Disallowing installation of component:
{5572161F-6A73-4552-91C7-8108C28DF8CE} since the same component with higher
versioned keyfile exists.
RemoveRelatedProduct does however happily remove the component.
Looks like an Installer limitation.
Klaus Gütter
-Ursprüngliche Nachricht-
Von: Phil Wilson [mailto:phildgwil...@gmail.com]
Gesendet: Montag, 24. November 2014 21:34
An: General discussion about the WiX toolset.
Betreff: Re: [WiX-users] Force overwrite DLL with previous version
inMajorUpgrade?
After InstallValidate should definitely work for a major upgrade. If that 2.4
version is not installed then you may have that MSI bug, especially if the file
is in the GAC or SxS
http://support.microsoft.com/kb/905238 and see if a repair restores the file.
Anyway, take a verbose log and search for the file name and its component id.
There are more routine possible issues, such as the component id being
inadvertently shared with something, and hopefully the Dll is marked as key
path.
---
Phil Wilson
On Mon, Nov 24, 2014 at 3:39 AM, Klaus Gütter klaus.guet...@it-gmbh.de wrote:
Hello,
I have the following situation: MyProduct version 1.1 uses ThirdPartyDll
version 2.5. For MyProduct version 1.2 we had to go back to ThirdPartyDll
version 2.4.
Is it possible to use an Major Upgrade in this situation? I had no luck with
this up to now:
- when scheduled afterInstallExecute, ThirdPartyDll version 2.5 is not
overwritten (as expected by the Installer rules)
- when scheduled afterInstallValidate, ThirdPartyDll version 2.5 is removed,
but version 2.4 is not installed.
If it matters: the MyProduct 1.1 setup was created with WiX 3.8, version 1.2
with WiX 3.9.
Klaus Gütter
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT
Server from Actuate! Instantly Supercharge Your Business Reports and
Dashboards with Interactivity, Sharing, Native Excel Exports, App
Integration more Get technology previously reserved for
billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.
clktrk ___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate!
Instantly Supercharge Your Business Reports and Dashboards with Interactivity,
Sharing, Native Excel Exports, App Integration more Get technology previously
reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
