Does it look like this?

http://support.microsoft.com/kb/905238

Phil Wilson


On Mon, Nov 4, 2013 at 9:55 AM, TimM <timmay...@smarttech.com> wrote:

> We have an install project that installs most of our public assemblies that
> are used by most of our various apps. The assembly components are all mark
> as permanent as we do not want them removed during uninstall.
>
> The issue that we seem to be are running into with one our assemblies is
> that when we upgrade to a newer version of one of the assemblies and run
> one
> of our older apps, that is still referencing the original assembly, then
> that app will fail with an assembly sxs error.
>
> Now we perform an major upgrade install on the installer that placed the
> assemblies there and therefore it uninstall that version first before
> installing the upgrade, but since the assemblies are all marked as
> permanent
> the older ones should have been left behind and therefore usable for older
> versions of the software.
>
> We checked the winsxs folder and the files/folders are there for both the
> new and older assemblies, but again the app does not find the older
> assemblies. I checked the install log and noticed that the
> MsiUnpublishAssemblies action was triggered and all the assemblies from the
> older version were unpublished. Are we suppose to turn off this action so
> that it can not unpublished any of the assemblies installed with this
> installer????
>
> Anyways this seems to only have occurred in this one case and therefore if
> the assemblies are all unpublished then we should have seen this issue long
> before now with any other older assemblies, so I looked further in the log
> and found near the end of the log mention of the assembly in question and
> it
> being triggered by the MsiProvideAssembly action. The only thing is that
> this MsiProvideAssembly is returning: 1607. So is this action trying to
> re-register the assembly but failing?
>
> I do not think many are handling assemblies like we are, but if anyone has
> any input as to what could be causing our issues I would like to hear from
> you....
>
> Thanks.
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Having-issues-with-permanently-installed-assemblies-and-Major-Upgrades-tp7590275.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Android is increasing in popularity, but the open development platform that
> developers love is also attractive to malware creators. Download this white
> paper to learn more about secure code signing practices that can help keep
> Android apps secure.
> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to