Never mind ... I just found the code signing section on Neil's blog here:
http://neilsleightholm.blogspot.com.au/2008/10/how-to-create-wix-build-machine.html
Thank-you
> To: wix-users@lists.sourceforge.net
> Date: Wed, 22 Feb 2012 11:44:12 +1100
> Subject: Re: [WiX-users] Burn Upgrade Scenario Issue
>
>
> I was using v3.6.221.0; I have now changed to v3.6.2617.0 and it seems to
> have resolved the problem. Thank-you Rob.
>
> However, my BA (using the new build) now only seems to launch correctly on
> the build system.
> If I attempt to run it on another machine it fails with:
>
> Loading managed bootstrapper application.
> Error 0x8013141a: Failed to create the managed bootstrapper application.
> Error 0x8013141a: Failed to create UX.
> Error 0x8013141a: Failed to load UX.
> Error 0x8013141a: Failed while running
> Error 0x8013141a: Failed to run per-user mode.
>
> I executed the WiX build ('make ship') from an elevated command window, and
> installed using the built WiX36.exe as usual.
> Obviously the build is being tied to my build system in some way ... any
> ideas?
>
>
> > What version of Burn are you using? Recent builds work better... the Beta
> > had a couple upgrade issues.
>
>
> >> To: wix-users@lists.sourceforge.net
> >> Date: Tue, 21 Feb 2012 14:51:30 +1100
> >> Subject: [WiX-users] Burn Upgrade Scenario Issue
> >>
> >>
> >> I have a custom Burn BA based on WixBA which is working well, until I try
> >> an upgrade scenario.
> >> The bundle chains together 3 msi's. (A, B and C)
> >> I install the bundle successfully.
> >> I then attempt to install an upgrade bundle where A and B are the original
> >> msi's but C is a major upgrade. The version of the bundle is also
> >> incremented.
> >> >From the logs I see that the BA detects A and B as present and required
> >> >as Present, and C as Absent, required Present. The related bundle is
> >> >detected as a major upgrade.
> >> The plan follows in the same fashion. So far so good.
> >> The apply is where things go wrong.
> >> The apply first applies the C upgrade as an install, which succeeds as
> >> expected.
> >> The apply then proceeds to uninstall the original bundle, which succeeds;
> >> and the apply is now complete.
> >>
> >> This scenario results in the old bundle uninstalled (correct) but the new
> >> bundle installed with only package C present, A and B are missing (they
> >> were uninstalled along with the original bundle).
> >> I am assuming that A and B should be given a RequestState of None when
> >> uninstalling the original bundle. However, they are incorrectly set to
> >> Absent. (C is correctly set to Superceded).
> >>
> >> Is there something obvious I am missing?
> >>
> >>
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
