If you've got the older assemblies marked permanent, then I'm guessing that
they are not in the newer major upgrade install. So the old product is
upgraded and removed but the assemblies stay behind, right? The alternative
would be to continue to ship the old and new assemblies for both old and
new versions of client apps, which would have been my inclination if
possible. Anyway, if that's what you're doing, this means that there is no
longer an actual owning product for that orphaned assembly (except for
system).and I think this means it has the potential to be unpublished
because only the file stays behind - publishing is related to the owning
products. That all assumes you're not shipping the older assemblies.

Also, it is still possible that http://support.microsoft.com/kb/905238 is
having an effect because any missing assemblies (the new one) are restored
by anything that prompts a repair, and so seeing both old and
new assemblies does not mean that you haven't got a problem related to this
bug. The description of the bug implies that the state of the old assembly
may not be correct because of registration with client products
(publishing), and that could lead to your error.  So the combination of
your permanent assembly and this bug is at least a working hypothesis. If
there was a repair that restored the new assembly there'll be an
MsiInstaller event log entry about it. In addition, this bug is fixed on
MSI 5.0 so that would mean this entire scenario is possible only prior to
Windows 7 and whatever server OS has 5.0.

Phil Wilson


On Mon, Nov 4, 2013 at 10:04 PM, Blair Murri <os...@live.com> wrote:

> Are there any policies set to redirect assemblies to alternate versions?
>
> What do the fusion logs say?
>
> > Date: Mon, 4 Nov 2013 15:23:37 -0600
> > From: ecyo...@grandecom.net
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] Having issues with permanently installed
> assemblies and Major Upgrades
> >
> > Does Registering the assemblies manually with this tool:
> >
> > http://msdn.microsoft.com/en-us/library/ex0ss12c.aspx
> >
> > solve the issue?
> >
> > Quoting TimM <timmay...@smarttech.com>:
> >
> > > Nope this is not the issue, because as I mentioned, the sxs folder and
> files
> > > for both versions do exists after the install and if it was like this
> > > article then the older version would be gone.
> > >
> > > So the files exist, but the app can not find the assembly, so this
> implies
> > > that the system no longer has that version registered even though the
> files
> > > and folders are intact. So again could the MsiUnpublishAssemblies and
> > > MsiProvideAssembly actions be causing the issue, or could there be
> some kind
> > > of conflict before the 2 versions that are causing the register of the
> new
> > > version to somehow override the registration of the older version?
> > >
> > > 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-tp7590275p7590278.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
>
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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

Reply via email to