Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch
The logs are no help at all, both the "good" patch and the "bad" patch have
pretty much the same log, there is no mention of "skipping installation of... "
in any log.
We have some advances, we do have some consistency when raising the version of
the PatchFamily AND the AssemblyFileVersionAttribute on the files.
We installed our patches with REINSTALLMODE=a and I think that's bad. Now we
are trying to see if we don't pass arguments and we do increase the versions if
it all gets patched...
So far seems working but for some reason the new files added in the patch don't
show in the installation directory after patch... they are in the msp file (I
can see with 7z).
Any ideas?
Thanks!
-Original Message-
From: Phil Wilson [mailto:phil.wil...@mvps.org]
Sent: יום ג 19 מרץ 2013 19:24
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede
first Patch
What about the log search results previously referred to? For completeness:
1) The component and features state for components installing patched files
should say something about whether they are to be installed. Examples:
MSI (s) (80:58) [16:44:49:982]: Feature: Setup; Installed: Local; Request:
Reinstall; Action: Reinstall
MSI (s) (80:58) [16:44:50:001]: Component: IniFile; Installed: Local;
Request: Local; Action: Local; Client State: Local
2) Check for component guids that refer to skipping or disallowing.
Examples:
MSI (c) (FC:18) [16:44:30:270]: skipping installation of assembly component:
{6C1B1CC2-C582-4CF0-BB1C-8B725D11AF78} since the assembly already exists
MSI (c) (FC:18) [16:44:30:749]: Disallowing installation of component:
{BCCE1657-D30B-498A-9EDA-D90FD2B858C2} since the same component with higher
versioned keyfile exists
3) Look for file activitity that says it's not being installed. Example:
MSI (s) (80:58) [16:45:21:077]: File: ; Won't Overwrite;
Won't patch;Existing file is of an equal version
4) I didn't mention adding files, not sure why you mentioned it, but if you
change or remove components in a patch you will see SELMGR entries in the log.
Do the install with MSIENFORCEUPGRADECOMPONENTRULES set to find out if you are
violating component rules.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370093(v=vs.85).as
px
The reason this matters is that removing components doesn't by default tell you
that something is wrong. The patch process will go into 'advertised'
state for the affected feature and files will not be patched.
Phil
-Original Message-
From: Tomer Cohen [mailto:tome...@qualisystems.com]
Sent: Tuesday, March 19, 2013 2:48 AM
To: General discussion for Windows Installer XML toolset.
Cc: Alex Abugov
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede
first Patch
Still having the same problem.
Tried different stuff:
Changing the AssemblyFileVersion of my compiled assemblies - didn't help.
Not adding new files in the patch - didn’t help.
Raising the PatchFamily Version attribute between patches - I'm not sure, in
consistent...
Removing the Supersede='yes' - didn't help.
Still having the same problem - first patch installs, all files are replaces as
desired, installing the second patch doesn't overwrite the assemblies but does
add new files, the second patch is shown in the add/remove updates.
Please give me directions to test, I'm working on solving this for 2 weeks
now... no luck, it seems random, sometimes working other times not.
Thanks.
-Original Message-
From: Tomer Cohen [mailto:tome...@qualisystems.com]
Sent: יום ה 14 מרץ 2013 08:50
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede
first Patch
Thanks for the prompt reply.
Here is the log snippet:
Machine policy value 'EnforceUpgradeComponentRules' is 0
SELMGR: New components have been added to feature 'ProductFeature'
SELMGR: Component 'QsTeamServer.x86.exe.config' is a new component added to
feature 'ProductFeature'
SELMGR: Component 'QsTeamServer.x86.exe' is a new component added to feature
'ProductFeature'
And then again later on:
Machine policy value 'EnforceUpgradeComponentRules' is 0
SELMGR: New components have been added to feature 'ProductFeature'
SELMGR: Component 'QsTeamServer.x86.exe.config' is a new component added to
feature 'ProductFeature'
SELMGR: Component 'QsTeamServer.x86.exe' is a new component added to feature
'ProductFeature'
Got lots of:
File: C:\Program Files\Qualisystems\TestShell Server\QS.Contracts.dll;
Overwrite; Won't patch;REINSTALLMODE specifies all files to be
overwritten
For all the files in the pat
Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch
Still having the same problem. Tried different stuff: Changing the AssemblyFileVersion of my compiled assemblies - didn't help. Not adding new files in the patch - didn’t help. Raising the PatchFamily Version attribute between patches - I'm not sure, in consistent... Removing the Supersede='yes' - didn't help. Still having the same problem - first patch installs, all files are replaces as desired, installing the second patch doesn't overwrite the assemblies but does add new files, the second patch is shown in the add/remove updates. Please give me directions to test, I'm working on solving this for 2 weeks now... no luck, it seems random, sometimes working other times not. Thanks. -----Original Message- From: Tomer Cohen [mailto:tome...@qualisystems.com] Sent: יום ה 14 מרץ 2013 08:50 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch Thanks for the prompt reply. Here is the log snippet: Machine policy value 'EnforceUpgradeComponentRules' is 0 SELMGR: New components have been added to feature 'ProductFeature' SELMGR: Component 'QsTeamServer.x86.exe.config' is a new component added to feature 'ProductFeature' SELMGR: Component 'QsTeamServer.x86.exe' is a new component added to feature 'ProductFeature' And then again later on: Machine policy value 'EnforceUpgradeComponentRules' is 0 SELMGR: New components have been added to feature 'ProductFeature' SELMGR: Component 'QsTeamServer.x86.exe.config' is a new component added to feature 'ProductFeature' SELMGR: Component 'QsTeamServer.x86.exe' is a new component added to feature 'ProductFeature' Got lots of: File: C:\Program Files\Qualisystems\TestShell Server\QS.Contracts.dll; Overwrite; Won't patch;REINSTALLMODE specifies all files to be overwritten For all the files in the patch... even though the log specifies it's gonna overwrite... it dones't. -Original Message- From: Phil Wilson [mailto:phil.wil...@mvps.org] Sent: יום ד 13 מרץ 2013 18:33 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch ...and to exapand on that, look for your files in the log. There should be a FileCopy that will say something like " Won't Overwrite;Won't patch; " and give you a reason. If your patch is incorrect because of component rules, look for SELMGR in the log and any remarks about removing components not supported. Phil -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, March 13, 2013 8:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch What does the action state for the *Components* show? That's what the Windows Installer is basing it's decision on. It would root cause the issue. It very likely could be the version of the files not changing but it would be best to *know* what fixed it, right? On Wed, Mar 13, 2013 at 8:18 AM, Tomer Cohen wrote: > Hi, > Thanks for the reply. > I have this in my log, this is the log of the second patch installation. > The MSP itself has all assemblies, but only installs those files below. > Patch Modified Files List: > MSI (s) (C4:04) [15:51:46:984]: File = > QualiSystems.ResourceManagement.Service.Plugin.config: Final State = > Install MSI (s) (C4:04) [15:51:46:984]: File = MRV_MCC_4640.exe: Final > State = Install MSI (s) (C4:04) [15:51:46:984]: File = > MRV_MCC_4840.exe: Final State = Install MSI (s) (C4:04) > [15:51:46:984]: File = ONPATH_HorizON_0204.exe: Final State = Install > MSI (s) (C4:04) [15:51:46:984]: File = > ONPATH_HorizON_0204_RuntimeConfig.xml: Final State = Install MSI (s) > (C4:04) [15:51:46:984]: File = SNMP_Manager.tslib: Final State = > Install MSI (s) (C4:04) [15:51:46:984]: File = TestShell_API.tslib: > Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = > ONPATH_HorizON_0244_RuntimeConfig.xml: Final State = Install MSI (s) > (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0244.exe: Final State = > Install > > I'll give the AssemblyFileVersion increment a chance. > Thanks. > > > > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: יום ד 13 מרץ 2013 17:06 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not > supersede first Patch > > What does the verbose log file in the patch say the action states for > the Components that you expect to be installed? Also, look a
Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch
Thanks for the prompt reply. Here is the log snippet: Machine policy value 'EnforceUpgradeComponentRules' is 0 SELMGR: New components have been added to feature 'ProductFeature' SELMGR: Component 'QsTeamServer.x86.exe.config' is a new component added to feature 'ProductFeature' SELMGR: Component 'QsTeamServer.x86.exe' is a new component added to feature 'ProductFeature' And then again later on: Machine policy value 'EnforceUpgradeComponentRules' is 0 SELMGR: New components have been added to feature 'ProductFeature' SELMGR: Component 'QsTeamServer.x86.exe.config' is a new component added to feature 'ProductFeature' SELMGR: Component 'QsTeamServer.x86.exe' is a new component added to feature 'ProductFeature' Got lots of: File: C:\Program Files\Qualisystems\TestShell Server\QS.Contracts.dll; Overwrite; Won't patch;REINSTALLMODE specifies all files to be overwritten For all the files in the patch... even though the log specifies it's gonna overwrite... it dones't. -Original Message- From: Phil Wilson [mailto:phil.wil...@mvps.org] Sent: יום ד 13 מרץ 2013 18:33 To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch ...and to exapand on that, look for your files in the log. There should be a FileCopy that will say something like " Won't Overwrite;Won't patch; " and give you a reason. If your patch is incorrect because of component rules, look for SELMGR in the log and any remarks about removing components not supported. Phil -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Wednesday, March 13, 2013 8:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch What does the action state for the *Components* show? That's what the Windows Installer is basing it's decision on. It would root cause the issue. It very likely could be the version of the files not changing but it would be best to *know* what fixed it, right? On Wed, Mar 13, 2013 at 8:18 AM, Tomer Cohen wrote: > Hi, > Thanks for the reply. > I have this in my log, this is the log of the second patch installation. > The MSP itself has all assemblies, but only installs those files below. > Patch Modified Files List: > MSI (s) (C4:04) [15:51:46:984]: File = > QualiSystems.ResourceManagement.Service.Plugin.config: Final State = > Install MSI (s) (C4:04) [15:51:46:984]: File = MRV_MCC_4640.exe: Final > State = Install MSI (s) (C4:04) [15:51:46:984]: File = > MRV_MCC_4840.exe: Final State = Install MSI (s) (C4:04) > [15:51:46:984]: File = ONPATH_HorizON_0204.exe: Final State = Install > MSI (s) (C4:04) [15:51:46:984]: File = > ONPATH_HorizON_0204_RuntimeConfig.xml: Final State = Install MSI (s) > (C4:04) [15:51:46:984]: File = SNMP_Manager.tslib: Final State = > Install MSI (s) (C4:04) [15:51:46:984]: File = TestShell_API.tslib: > Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = > ONPATH_HorizON_0244_RuntimeConfig.xml: Final State = Install MSI (s) > (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0244.exe: Final State = > Install > > I'll give the AssemblyFileVersion increment a chance. > Thanks. > > > > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: יום ד 13 מרץ 2013 17:06 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not > supersede first Patch > > What does the verbose log file in the patch say the action states for > the Components that you expect to be installed? Also, look at the File > install log lines, those usually have quite a bit information about > when the file is being applied and whether it is being patched. > > > On Wed, Mar 13, 2013 at 7:19 AM, Tomer Cohen >wrote: > > > Just to be clear, the files don't have a newer version, but they are > > different in size and binary... > > > > -Original Message- > > From: David Watson [mailto:dwat...@sdl.com] > > Sent: יום ד 13 מרץ 2013 16:04 > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does > > not supersede first Patch > > > > Did you increase the assemblyfileversion of those dlls? > > > > -Original Message- > > From: Tomer Cohen [mailto:tome...@qualisystems.com] > > Sent: 13 March 2013 13:28 > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-us
Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch
Hi, Thanks for the reply. I have this in my log, this is the log of the second patch installation. The MSP itself has all assemblies, but only installs those files below. Patch Modified Files List: MSI (s) (C4:04) [15:51:46:984]: File = QualiSystems.ResourceManagement.Service.Plugin.config: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = MRV_MCC_4640.exe: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = MRV_MCC_4840.exe: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0204.exe: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0204_RuntimeConfig.xml: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = SNMP_Manager.tslib: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = TestShell_API.tslib: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0244_RuntimeConfig.xml: Final State = Install MSI (s) (C4:04) [15:51:46:984]: File = ONPATH_HorizON_0244.exe: Final State = Install I'll give the AssemblyFileVersion increment a chance. Thanks. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: יום ד 13 מרץ 2013 17:06 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch What does the verbose log file in the patch say the action states for the Components that you expect to be installed? Also, look at the File install log lines, those usually have quite a bit information about when the file is being applied and whether it is being patched. On Wed, Mar 13, 2013 at 7:19 AM, Tomer Cohen wrote: > Just to be clear, the files don't have a newer version, but they are > different in size and binary... > > -Original Message- > From: David Watson [mailto:dwat...@sdl.com] > Sent: יום ד 13 מרץ 2013 16:04 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not > supersede first Patch > > Did you increase the assemblyfileversion of those dlls? > > -Original Message- > From: Tomer Cohen [mailto:tome...@qualisystems.com] > Sent: 13 March 2013 13:28 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not > supersede first Patch > > No no, you got me all wrong. > I don't want cumulative patches! The opposite, I want the last patch > that I install to supersede all others, overwriting the files. > > I have the MSP file and in z7 I can see that it has all the "right" > files, that is the new files. But if I install it after I installed an > earlier patch... those files don't get to the installation folder...?! I'm > using: > msiexec.exe /L*v c:\temp\log.txt /p "c:\temp\patch2\patch.msp" > REINSTALL=ALL REINSTALLMODE=aumsv ADDLOCAL=ALL REBOOT=ReallySuppress > the log of the second patch installation: > Note: 1: 2228 2: 3: MsiAssembly 4: SELECT > `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, > `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM > `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_` = > `Component`.`Component` AND `MsiAssembly`.`Component_` = ? > MSI (s) (48:C4) [15:13:42:791]: Patch Modified Files List: > //it gives only a partial list of the files that are in the MSP file... > allthose files are !NOT! .NET dlls, the .NET dlls are the files that > don't get overwritten for some reason... > > Please help! Thanks. > > Tomer Cohen > InSight Team Leader, R&D > QualiSystems > Mobile: +972-52-3362846 > Email: tome...@qualisystems.com > Web: www.qualisystems.com > > -Original Message- > From: Brian_Covington [mailto:briancoving...@yahoo.com] > Sent: יום ד 13 מרץ 2013 06:02 > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not > supersede first Patch > > Sorry, no. We are weeks away from having to release and the plan for > now is to not use cumulative patches. > > > > > From: Tomer Cohen [via Windows Installer XML (WiX) toolset] < > ml-node+s687559n758426...@n2.nabble.com> > To: Brian_Covington > Sent: Tuesday, March 12, 2013 10:11 AM > Subject: Re: Managed Bootstrapper - Second Patch does not supersede > first Patch > > > Got anywhere with this? I have the same problem > I don't mind having both patches appear in the add remove - updates > side by side, but the second patch doesn't replace the files at all... > If I install it without the first patch already installed then that > patch works great. > > Tomer. > Thanks. > > -Original Messag
Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch
Just to be clear, the files don't have a newer version, but they are different
in size and binary...
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: יום ד 13 מרץ 2013 16:04
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede
first Patch
Did you increase the assemblyfileversion of those dlls?
-Original Message-
From: Tomer Cohen [mailto:tome...@qualisystems.com]
Sent: 13 March 2013 13:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede
first Patch
No no, you got me all wrong.
I don't want cumulative patches! The opposite, I want the last patch that I
install to supersede all others, overwriting the files.
I have the MSP file and in z7 I can see that it has all the "right" files, that
is the new files. But if I install it after I installed an earlier patch...
those files don't get to the installation folder...?! I'm using:
msiexec.exe /L*v c:\temp\log.txt /p "c:\temp\patch2\patch.msp" REINSTALL=ALL
REINSTALLMODE=aumsv ADDLOCAL=ALL REBOOT=ReallySuppress the log of the second
patch installation:
Note: 1: 2228 2: 3: MsiAssembly 4: SELECT `MsiAssembly`.`Attributes`,
`MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`,
`Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE
`MsiAssembly`.`Component_` = `Component`.`Component` AND
`MsiAssembly`.`Component_` = ?
MSI (s) (48:C4) [15:13:42:791]: Patch Modified Files List:
//it gives only a partial list of the files that are in the MSP file...
allthose files are !NOT! .NET dlls, the .NET dlls are the files that don't get
overwritten for some reason...
Please help! Thanks.
Tomer Cohen
InSight Team Leader, R&D
QualiSystems
Mobile: +972-52-3362846
Email: tome...@qualisystems.com
Web: www.qualisystems.com
-Original Message-
From: Brian_Covington [mailto:briancoving...@yahoo.com]
Sent: יום ד 13 מרץ 2013 06:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede
first Patch
Sorry, no. We are weeks away from having to release and the plan for now is to
not use cumulative patches.
____
From: Tomer Cohen [via Windows Installer XML (WiX) toolset]
To: Brian_Covington
Sent: Tuesday, March 12, 2013 10:11 AM
Subject: Re: Managed Bootstrapper - Second Patch does not supersede first Patch
Got anywhere with this? I have the same problem
I don't mind having both patches appear in the add remove - updates side by
side, but the second patch doesn't replace the files at all...
If I install it without the first patch already installed then that patch works
great.
Tomer.
Thanks.
-Original Message-
From: Brian_Covington [mailto:[hidden email]]
Sent: יום ה 15 נובמבר 2012 00:41
To: [hidden email]
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede
first Patch
Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and
10.00.37.0004 (HF2).
I am changing the bundle version as well as the version of the msi, but still
the second patch for the bundle appears alongside the first one, not replacing
it as I would expect.
Do I need to do something to "hide" the first patch when the second one is
applied? And if so, how would I undo this when uninstalling the second patch?
As these are cumulative, removable patches, only one entry must exist in the
"Installed Updates" of ARP.
I do see where it realized the first patch bundle was installed, but did
nothing with it.
Plan 3 packages, action: Install
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: Netfx4Full
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: S3DInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable
'WixBundleLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C1
93CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch.log'
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable
'WixBundleRollbackLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C1
93CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch_rollback.log'
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: RADInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Planned package: Netfx4Full, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[0F98:0E38][2012-11-14T16:19:55]: Planned package: S3DInstallPatch, state:
Absent, default requested: Pres
Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch
No... there is nothing in the documentation about that...
Won't it make the .NET stop working, the assemblies are signed... if some are
not in the same version, it won't find them...
Thanks for the fast reply. :)
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: יום ד 13 מרץ 2013 16:04
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede
first Patch
Did you increase the assemblyfileversion of those dlls?
-Original Message-----
From: Tomer Cohen [mailto:tome...@qualisystems.com]
Sent: 13 March 2013 13:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede
first Patch
No no, you got me all wrong.
I don't want cumulative patches! The opposite, I want the last patch that I
install to supersede all others, overwriting the files.
I have the MSP file and in z7 I can see that it has all the "right" files, that
is the new files. But if I install it after I installed an earlier patch...
those files don't get to the installation folder...?! I'm using:
msiexec.exe /L*v c:\temp\log.txt /p "c:\temp\patch2\patch.msp" REINSTALL=ALL
REINSTALLMODE=aumsv ADDLOCAL=ALL REBOOT=ReallySuppress the log of the second
patch installation:
Note: 1: 2228 2: 3: MsiAssembly 4: SELECT `MsiAssembly`.`Attributes`,
`MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`,
`Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE
`MsiAssembly`.`Component_` = `Component`.`Component` AND
`MsiAssembly`.`Component_` = ?
MSI (s) (48:C4) [15:13:42:791]: Patch Modified Files List:
//it gives only a partial list of the files that are in the MSP file...
allthose files are !NOT! .NET dlls, the .NET dlls are the files that don't get
overwritten for some reason...
Please help! Thanks.
Tomer Cohen
InSight Team Leader, R&D
QualiSystems
Mobile: +972-52-3362846
Email: tome...@qualisystems.com
Web: www.qualisystems.com
-Original Message-
From: Brian_Covington [mailto:briancoving...@yahoo.com]
Sent: יום ד 13 מרץ 2013 06:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede
first Patch
Sorry, no. We are weeks away from having to release and the plan for now is to
not use cumulative patches.
From: Tomer Cohen [via Windows Installer XML (WiX) toolset]
To: Brian_Covington
Sent: Tuesday, March 12, 2013 10:11 AM
Subject: Re: Managed Bootstrapper - Second Patch does not supersede first Patch
Got anywhere with this? I have the same problem
I don't mind having both patches appear in the add remove - updates side by
side, but the second patch doesn't replace the files at all...
If I install it without the first patch already installed then that patch works
great.
Tomer.
Thanks.
-Original Message-
From: Brian_Covington [mailto:[hidden email]]
Sent: יום ה 15 נובמבר 2012 00:41
To: [hidden email]
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede
first Patch
Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and
10.00.37.0004 (HF2).
I am changing the bundle version as well as the version of the msi, but still
the second patch for the bundle appears alongside the first one, not replacing
it as I would expect.
Do I need to do something to "hide" the first patch when the second one is
applied? And if so, how would I undo this when uninstalling the second patch?
As these are cumulative, removable patches, only one entry must exist in the
"Installed Updates" of ARP.
I do see where it realized the first patch bundle was installed, but did
nothing with it.
Plan 3 packages, action: Install
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: Netfx4Full
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: S3DInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable
'WixBundleLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C1
93CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch.log'
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable
'WixBundleRollbackLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C1
93CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch_rollback.log'
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: RADInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Planned package: Netfx4Full, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, depende
Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch
No no, you got me all wrong.
I don't want cumulative patches! The opposite, I want the last patch that I
install to supersede all others, overwriting the files.
I have the MSP file and in z7 I can see that it has all the "right" files, that
is the new files. But if I install it after I installed an earlier patch...
those files don't get to the installation folder...?! I'm using:
msiexec.exe /L*v c:\temp\log.txt /p "c:\temp\patch2\patch.msp" REINSTALL=ALL
REINSTALLMODE=aumsv ADDLOCAL=ALL REBOOT=ReallySuppress
the log of the second patch installation:
Note: 1: 2228 2: 3: MsiAssembly 4: SELECT `MsiAssembly`.`Attributes`,
`MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`,
`Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE
`MsiAssembly`.`Component_` = `Component`.`Component` AND
`MsiAssembly`.`Component_` = ?
MSI (s) (48:C4) [15:13:42:791]: Patch Modified Files List:
//it gives only a partial list of the files that are in the MSP file...
allthose files are !NOT! .NET dlls, the .NET dlls are the files that don't get
overwritten for some reason...
Please help! Thanks.
Tomer Cohen
InSight Team Leader, R&D
QualiSystems
Mobile: +972-52-3362846
Email: tome...@qualisystems.com
Web: www.qualisystems.com
-Original Message-
From: Brian_Covington [mailto:briancoving...@yahoo.com]
Sent: יום ד 13 מרץ 2013 06:02
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede
first Patch
Sorry, no. We are weeks away from having to release and the plan for now is to
not use cumulative patches.
____
From: Tomer Cohen [via Windows Installer XML (WiX) toolset]
To: Brian_Covington
Sent: Tuesday, March 12, 2013 10:11 AM
Subject: Re: Managed Bootstrapper - Second Patch does not supersede first Patch
Got anywhere with this? I have the same problem
I don't mind having both patches appear in the add remove - updates side by
side, but the second patch doesn't replace the files at all...
If I install it without the first patch already installed then that patch works
great.
Tomer.
Thanks.
-Original Message-
From: Brian_Covington [mailto:[hidden email]]
Sent: יום ה 15 נובמבר 2012 00:41
To: [hidden email]
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede
first Patch
Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and
10.00.37.0004 (HF2).
I am changing the bundle version as well as the version of the msi, but still
the second patch for the bundle appears alongside the first one, not replacing
it as I would expect.
Do I need to do something to "hide" the first patch when the second one is
applied? And if so, how would I undo this when uninstalling the second patch?
As these are cumulative, removable patches, only one entry must exist in the
"Installed Updates" of ARP.
I do see where it realized the first patch bundle was installed, but did
nothing with it.
Plan 3 packages, action: Install
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: Netfx4Full
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: S3DInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable
'WixBundleLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C193CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch.log'
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable
'WixBundleRollbackLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C193CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch_rollback.log'
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: RADInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Planned package: Netfx4Full, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[0F98:0E38][2012-11-14T16:19:55]: Planned package: S3DInstallPatch, state:
Absent, default requested: Present, ba requested: Present, execute: Install,
rollback: Uninstall, cache: Yes, uncache: No, dependency: None
[0F98:0E38][2012-11-14T16:19:55]: Planned package: RADInstallPatch, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
*[0F98:0E38][2012-11-14T16:19:55]: Planned related bundle:
{1ca42db4-c103-4fa2-ba05-d3c20f8f5d70}, type: Dependent, default requested:
None, ba requested: None, execute: None, rollback: None, dependency: None*
Then in the msi install log, I see
Final Patch Application Order:
MSI (s) (44:2C) [16:20:06:348]: {379A67FF-1175-42B8-B7B7-
Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede first Patch
Got anywhere with this? I have the same problem
I don't mind having both patches appear in the add remove - updates side by
side, but the second patch doesn't replace the files at all...
If I install it without the first patch already installed then that patch works
great.
Tomer.
Thanks.
-Original Message-
From: Brian_Covington [mailto:briancoving...@yahoo.com]
Sent: יום ה 15 נובמבר 2012 00:41
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not supersede
first Patch
Same results with versions 10.00.35.0004, 10.00.36.0004 (HF1), and
10.00.37.0004 (HF2).
I am changing the bundle version as well as the version of the msi, but still
the second patch for the bundle appears alongside the first one, not replacing
it as I would expect.
Do I need to do something to "hide" the first patch when the second one is
applied? And if so, how would I undo this when uninstalling the second patch?
As these are cumulative, removable patches, only one entry must exist in the
"Installed Updates" of ARP.
I do see where it realized the first patch bundle was installed, but did
nothing with it.
Plan 3 packages, action: Install
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: Netfx4Full
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: S3DInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable
'WixBundleLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C193CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch.log'
[0F98:0E38][2012-11-14T16:19:55]: Setting string variable
'WixBundleRollbackLog_S3DInstallPatch' to value
'C:\Users\sp3dtest\AppData\Local\Temp\PRODUCT_S3D_HotFix_2_20121114161952_{C193CA79-FACC-4874-AF85-6CCC6B10851C}_0_S3DInstallPatch_rollback.log'
[0F98:0E38][2012-11-14T16:19:55]: Skipping dependency registration on package
with no dependency providers: RADInstallPatch
[0F98:0E38][2012-11-14T16:19:55]: Planned package: Netfx4Full, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
[0F98:0E38][2012-11-14T16:19:55]: Planned package: S3DInstallPatch, state:
Absent, default requested: Present, ba requested: Present, execute: Install,
rollback: Uninstall, cache: Yes, uncache: No, dependency: None
[0F98:0E38][2012-11-14T16:19:55]: Planned package: RADInstallPatch, state:
Present, default requested: Present, ba requested: Present, execute: None,
rollback: None, cache: No, uncache: No, dependency: None
*[0F98:0E38][2012-11-14T16:19:55]: Planned related bundle:
{1ca42db4-c103-4fa2-ba05-d3c20f8f5d70}, type: Dependent, default requested:
None, ba requested: None, execute: None, rollback: None, dependency: None*
Then in the msi install log, I see
Final Patch Application Order:
MSI (s) (44:2C) [16:20:06:348]: {379A67FF-1175-42B8-B7B7-8F8ED98CA7EB} -
C:\ProgramData\Package
Cache\{379A67FF-1175-42B8-B7B7-8F8ED98CA7EB}\S3DInstallPatch
MSI (s) (44:2C) [16:20:06:349]: Other Patches:
*MSI (s) (44:2C) [16:20:06:349]: Superseded:
{ADC561F5-6FC8-4EA1-8DB1-E79A7F18A7DD} - *
Which I can only assume is the First Patch being superseeded, so it looks like
the MSI is correct, just not the Bootstrapper.
Is no one else facing this problem? Or does no one do cumulative patching?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-Bootstrapper-Second-Patch-does-not-supersede-first-Patch-tp7581779p7581928.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Monitor your physical, virtual and cloud infrastructure from a single web
console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud
infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
--
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] UNSUBSCRIBE
UNSUBSCRIBE -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] InstallAware Help...
Hi, Looking for help with upgrading a product previously installed by InstallAware, now we are using WIX. Thanks. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
