Burn should automatically detect when you are doing an minor upgrade and pass the appropriate switches for you.
On Thu, Jan 3, 2013 at 3:57 AM, Gustavo Gustavo <dotnetdev.java...@gmail.com > wrote: > Hi, > > I need to implement minor upgrades - same ProductCode for my software > releases. > > The problem is that when it's a fresh new installation it's enough to > double click the .msi (or msiexec /i <awesome-software.msi>). > > But, when it’s an upgrade, then I need to msiexec /i <awesome-software.msi> > REINSTALL=ALL REINSTALLMODE=vomus only. > > I would like to handle upgrades with the same manner as a fresh new > installation – simply double clicking the .msi. > > I was able to handle it before by having Major Upgrades, but then, came up > a requirement that we must keep the same ProductCode across the releases > (explanation why at the bottom). > > Well, I was thinking of having a bootstrapper (then an .exe instead of a > .msi) to handle this logic, and shield the user from this problem. > > Seems like from WiX 3.6 on, the way to go is to create a bundle with Burn > Engine. > > That’s OK. I’ll have a bundle with two MsiPackage pointing to the same > awesome-software.msi, but one will have the properties REINSTALL=ALL and > REINSTALLMODE=vomus set via children MsiProperty elements. > > Then, I need some sort of logic to handle which one will be triggered by > the bootstrapper. I guess that I can use a ProductSearch to check if the > ProductCode is already in place. Then, based on the variable set, for each > MsiPackage I’ll have a InstallCondition. > > Am I going in the right direction? Is this is the way to go? > > Or should I think of .msp (and all the overhead of creating and managing > them) or create a boostrapper myself, without WiX Burn? > > -> Motivation behind Major/Minor upgrade strategy: > > Before, we had Major Upgrades, therefore, every upgrade was in fact an > uninstall/install. But then another product, awesome-bundle.exe, included > awesome-software.msi within their bundle (built with WiX 3.6 Burn). If > awesome-software.msi was upgraded in a stand-alone fashion (thus changing > the ProductCode), then awesome-bundle.exe wasn’t able to remove it anymore, > since the ProductCode changed and it had lost track of > awesome-software.msi. So this means that Burn doesn’t support Major > Upgrades on its packages? > > Kind Regards, > Gustavo > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122712 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_122712 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
