Hi everyone, I have a little problem with my burn / msi installer:
My "old" MSI-installer has been replaced by a burn-package that includes multiple MSIs (as one of the components that was a merge-module the old MSI is now in use by 3rd parties as well). Unfortunately - due to my lack of knowledge at that time - I did not include a MajorUpgrade element in my old MSI. To remedy this, I have tried the following approach: My old MSI (msiOld) is uninstalled via my new MSI (msiNew). I want to install a second MSI (msiBlock) after msiNew to block any future installation of my msiOld to not mess up my new (and future) installation(s). Unfortunately, burn sees the msiOld and when msiBlock is scheduled it is scheduled as a minor install because burn thinks that msiOld is still on the system even though it has been uninstalled by msiNew. Is there any way that I can force burn to still install msiBlock as a major install? Or is there any way to tell burn that it needs to re-evaluate what is installed on the system after msiNew has been installed (and thus msiOld uninstalled) prior to installing msiBlock? Best regards, Tobias ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
