This is possible. First the new B.exe needs a higher Bundle/@Version than any previously released Bundle. You can give the new B.exe one of the existing UpgradeCodes or give it a new one. The important thing is to add RelatedBundle elements where the Id attribute is set to the UpgradeCode of the old Bundle you want to upgrade. You also need to add Action='Upgrade'.
The Bundle/@UpgradeCode is just a (required) shortcut to define <RelatedBundle Id='guid' Action='Upgrade'/> . Remember, make the new Bundle version higher than all the existing Bundles or it will not choose to upgrade. On Wed, Apr 3, 2013 at 12:38 PM, ptr <ptrajku...@gmail.com> wrote: > hey all > > I have a bundle B.exe that installs NET4.exe , VS2010CRT.msi , > OurProduct.msi. The bundle is compressed and embeds all the packages. > > NET4.msi being the .NET 4 full framework > VS2010CRT.msi being VS2010 CRT runtimes > OurProduct.msi being all the assemblies that we develop inhouse. > > We support both 32bit and 64bit platforms *but don't allow the user to > install a 32bit version on a 64bit OS.* > > B.exe (32bit) B.exe(64bit) have different upgrade codes and so do > VS2010CRT.msi and OurProduct.msi as per recommendations I found on the web > in case one wants to support a side by side install. > > Lot of our customers already have NET4 framework installed so I made > boostrapper W.exe that can download NET4.exe , VS2010CRT.msi , > OurProduct.msi if needed from our webservers. This way the bootstrapper > can itself be very small in size. This seems to work beautifully. But this > has a problem that I would need W.exe 32bit and W.exe 64bit. > > Now I am thinking of making a universal web installer U.exe that would > embed NET4.exe VS2010-32msi VS2010-64bit.msi Ourproduct64bit.msi > Ourproduct32.msi and install only the components needed based on whether > the current OS is 32bit or 64bit. > > If I want to support a scenarios where the user > 1) installs using B.exe > 2) upgrades using U.exe > 3) upgrades using B.exe > > and it all works seamlessly. > > It seems like this would work in theory if B.exe (32bit) , B.exe (64bit) > and U.exe all would have to share the same upgrade code. Would this work or > is there another recommended way to achieve what I want ? > > > Thanks > raj > > ------------------------------------------------------------------------------ > Minimize network downtime and maximize team effectiveness. > Reduce network management and security costs.Learn how to hire > the most talented Cisco Certified professionals. Visit the > Employer Resources Portal > http://www.cisco.com/web/learning/employer_resources/index.html > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
