The upgrade is an uninstall of the old product, using the VS setup, so if it's true that the VS setup is removing files when it uninstalls then there really isn't much you can do. That uninstall will do what it does, and it looks like it makes no differentiation between being uninstalled and being upgraded (when it would presumably leave data behind). Avoiding RemoveExistingProducts won't solve that problem.
Depending on where you sequenced RemoveExistingProducts and how you built your new MSI file you'll get a variety of results. VS setups don't expose component guids, so if your new setup doesn't have the same guids for the same files and registry items then REP sequenced at the end will not work reliably. If that's the case, your best bet is to sequence REP early so it removes the old product first and then installs the new one. That will get you a clean upgrade. As Rob says, why avoid that? It won't solve your problem with removed files if the old uninstall is determined to uninstall them. That would need a program to run before your upgrade and locate and save the data files somewhere. --------------- Phil Wilson On Tue, Jul 15, 2014 at 8:43 AM, barthooper <matthew.a.ma...@gmail.com> wrote: > I have been able to remove the old MSI but as part of the uninstall for the > original MSI, some data stored in ProgramData is removed, as well as some > data files that are stored in the actual Applications folder. > > The goal was to try to make the upgrade process as smooth as possible. I > originally tried to just use FindRelatedProducts and then attempted to use > the original UpgradeCode from the old project as the UpgradeCode for first > the MSI and then for the Bundle. > > > Rob Mensching-7 wrote >> Your new MSI should be able to remove the old MSI if you get the upgrade >> information correct. That will use REmoveExistingProducts. Not clear why >> you want to avoid that. >> >> _______________________________________________________________ >> FireGiant | Dedicated support for the WiX toolset | >> http://www.firegiant.com/ >> >> -----Original Message----- >> From: barthooper [mailto: > >> matthew.a.mains@ > >> ] >> Sent: Tuesday, July 15, 2014 8:25 AM >> To: > >> wix-users@.sourceforge > >> Subject: [WiX-users] UpgradeCode question: Moving from VS Setup Project to >> WiX and Burn >> >> Hello everyone, >> >> I'm wondering if it is possible to have an existing product that was >> installed using a Visual Studio Setup Project be migrated so that the MSI >> is part of a Burn bundle and the upgrade process does not involve >> RemoveExistingProducts. >> >> The new Burn bundle contains many of the same files as the original, but >> quite a few have changes, as well as adding additional folders and >> registry entries not included in the old install, and installing >> additional packages as part of the bundle. >> >> I've read so much online about UpgradeCode and Upgrade elements and the >> vast majority of the examples refer to RemoveExistingProducts. Are there >> any realistic options for an approach similar to the above? It would be >> vastly preferable to just add to the existing files as there is user >> specific data associated with existing installs. >> >> I've tried having the MSI use the original UpgradeCode, as well as using >> it in the Burn bundle itself to no avail. >> >> >> >> -- >> View this message in context: >> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/UpgradeCode-question-Moving-from-VS-Setup-Project-to-WiX-and-Burn-tp7595846.html >> Sent from the wix-users mailing list archive at Nabble.com. >> >> ------------------------------------------------------------------------------ >> Want fast and easy access to all the code in your enterprise? Index and >> search up to 200,000 lines of code with a free copy of Black Duck Code >> Sight - the same software that powers the world's largest code search on >> Ohloh, the Black Duck Open Hub! Try it now. >> http://p.sf.net/sfu/bds >> _______________________________________________ >> WiX-users mailing list > >> WiX-users@.sourceforge > >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> ------------------------------------------------------------------------------ >> Want fast and easy access to all the code in your enterprise? Index and >> search up to 200,000 lines of code with a free copy of Black Duck >> Code Sight - the same software that powers the world's largest code >> search on Ohloh, the Black Duck Open Hub! Try it now. >> http://p.sf.net/sfu/bds >> _______________________________________________ >> WiX-users mailing list > >> WiX-users@.sourceforge > >> https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > -- > View this message in context: > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/UpgradeCode-question-Moving-from-VS-Setup-Project-to-WiX-and-Burn-tp7595846p7595849.html > Sent from the wix-users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
