I believe I found a way to accomplish this. Using the OnExit=error as well as some other properties I already had setup seems to be working.
On Tue, Feb 22, 2011 at 3:38 PM, Andy Clugston <clug...@gmail.com> wrote: > All, > > I currently have the "prevent downgrade custom action" below... > > <Custom Action='NoDowngradeAction' > After='FindRelatedProducts'>NEWERFOUND</Custom> > <CustomAction Id='NoDowngradeAction' Error='Installation aborted. A later > version of [ProductName] is already installed.' /> > > One thing that I am tasked to support is updating of a product at runtime. > So, shutting down the app(s), invoking msiexec, and starting them back up. > The "starting them back up" is handled by custom actions in the MSI. The one > use case that I am having trouble with is when an older version of the > product is attempted to be installed on a system when a newer version > already exists. The action above takes care of it, but I still need to > restart the application. It appears that the "Error" handler causes an > immediate exit of msiexec. I have tried to place my app-startup action > before and after NoDowngradeAction, but in both cases the custom action is > not called. The app-startup custom action is of type "immediate". > > As always, any advice is appreciated. > > Thanks. > ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
