Okay thanks for all your help/suggestions, but have found what the actual issue was. The MsiProvideAssembly returning: 1607 on 2 assemblies was actually the hint.
After testing a few times I got it to the point where 2 assemblies were gone after the upgrade and they were the ones listed in the MsiProvideAssembly actions. And the 1607 basically means that the components ID could not be found. So I checked the component GUID's of the new updated components and found out that they were the same as the older versions that were installed. So I changed the GUID of one of the assemblies and sure enough that fixed the issue.... I have mentioned many times, to our install developers, that if we have updated assemblies that we should be changing the GUID's so that there are no conflicts if both assemblies are install, but I guess that when these ones were upgraded the GUID change never happened. Anyways problem now fixed and therefore on to the next....... -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Having-issues-with-permanently-installed-assemblies-and-Major-Upgrades-tp7590275p7590297.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
