Since two people have already noted this is really hackish, I think the way to get a) is:
1. Mark the MsiPackage/@Permanent='yes'. That will prevent uninstall. 2. Make the ExePackage/@DetectCondition true even though the MSI is not yet installed. That way Burn thinks there is nothing to do on install and will run the UninstallCommand during uninstall. This is incredibly hackish. On Sat, Mar 2, 2013 at 1:10 AM, Neil Sleightholm <n...@x2systems.com> wrote: > Personally I'd go for (a) - I have had to do something similar for an old > WISE authored product. > > Can you run the uninstall on the MSI and then run the exe to do the final > clean-up? You could then author the bundle as normal for the > MSI/TRANSFORM/MSP and the write a custom exe or msi to just run the > clean-up on uninstall. In my case I actually was able to write an MSI with > custom actions to do the clean-up and I scheduled them to only run on > uninstall. > > One problem I had was how to handle upgrades but with more hacking I found > a solution, bottom line is that the installer really ought to be fixed. > > -----Original Message----- > From: Christopher Painter [mailto:chr...@iswix.com] > Sent: 28 February 2013 21:35 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Burn Install / Uninstall Scenario > > > > I've got a weird scenario involving AdobeFlash. They have an MSI, > TRANSFORM and MSP that I need to use to install. However, their uninstall > is broken (incomplete) and they provide an EXE to run to do a complete > uninstall. > > We created a bundle to lay this all down but we are getting stuck on the > uninstall side. We want either > > a) Burn runs the MSI for install but not uninstall and run the EXE for > uninstall of the MSI (but has no install) > a1) I can think of a way of creating a man in the middle EXE to handle > both install and uninstall but this is hackish. > > b) Have burn install everything but never register the bundle with the > system. We tried the DisableRepair/Remove/Change and while it doesn't show > in ARP, a second run of the EXE shows the meta is present on the system. > > > (b) is a viable option for us because SCCM can run burn to do the install > and run the EXE provided by Adobve for the uninstall. > > Any thoughts? > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
