REP is right after InstallInitialize. I can't put this Rollback action in the older MSI. Here is the reason why. I am installing drivers using custom actions. When installing the newer version as part of the upgrade, say something goes wrong with the driver installation. At this point a rollback is initiated and I need the drivers to rollback to the version before the upgrade even started. The method I am using for driver installation doesn't support rollback, so the only thing I can do is re-install the older version. However I need an INF file that is part of the original installation (before starting installation process). Where would I put my rollback action to be able to access this pre-existing INF file?
Richard-45 wrote: > > > In article > <048288cf0239f24a8c2299e69f020b0501293...@exchange.panologic.com>, > "Ashwin Chandra" <achan...@panologic.com> writes: > >> I am trying to perform a rollback custom action when an upgrade install >> fails. However, I require the original files on the system (before the >> installer updates them) to execute this rollback custom action. >> [...] > > RemoveExistingProducts is the standard action that removes previous > versions of the application before installing the current one. > > Where do you have REP sequenced in your upgrade? > > It sounds to me like your rollback action should be in the MSI of the > old version being upgraded rather than in the MSI of the new version. > You can do this by applying a patch to the existing version before > upgrading, using a bootstrapper. > > I've done these sorts of things where a failed upgrade has to be > patched up in order for the manual uninstall of the previous version > or the next upgrade attempt to succeed. I've compensated for buggy > prior versions both by patching the previous version before updating > and by putting special error handling code in the bootstrapper that > executed the upgrade. It feels a little bit ugly, but it works. As > for when you do one and not the other, well, I patched stuff in the > existing product MSI when I needed to do adjust the behavior of > something that was essentially in the middle of the install > transaction for the previous version. For cleaning up after a failed > upgrade, I put that in the bootstrapper since it didn't involve > applying a patch to the previous version (risky for us at the time) > and we already required a bootstrapper anyway. > -- > "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download > <http://www.xmission.com/~legalize/book/download/index.html> > > Legalize Adulthood! <http://blogs.xmission.com/legalize/> > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK > i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- View this message in context: http://n2.nabble.com/Rollback-Custom-Action-during-Upgrade-tp2866142p2866280.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
