Thanks for mentioning those hotfixes.
In the end I've included them in the bootstrapper. It seems to be the right
way compared to increasing the file version of the assemblies.
--
View this message in context:
I've done some more tests and it seems that on Windows Installer 4.5 the
assembly is removed from GAC after a major upgrade.
Good to see that at least on 5.0 got fixed.
--
View this message in context:
]
Sent: Tuesday, January 03, 2012 1:09 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] RemoveExistingProducts after the InstallFinalize
action still needed so that Major Upgrades don't remove assembly from GAC ?
I've done some more tests and it seems that on Windows Installer 4.5
Hi,
There is http://support.microsoft.com/kb/905238 a knowledge base article
(mentioned also on the WiX Documentation) that describes the case of an
assembly from GAC missing after a major upgrade. One of the solutions was to
schedule *RemoveExistingProducts *action to occur after the
still needed so that Major Upgrades don't remove assembly from GAC ?
Hi,
There is http://support.microsoft.com/kb/905238 a knowledge base article
(mentioned also on the WiX Documentation) that describes the case of an
assembly from GAC missing after a major upgrade. One of the solutions
toolset.
Subject: Re: [WiX-users] RemoveExistingProducts after the InstallFinalize
action still needed so that Major Upgrades don't remove assembly from GAC ?
My colleague investigated some scenarios like this a few months ago. He found
that when not changing the assembly version, then using the -fv
6 matches
Mail list logo