Windows Installer sets that if a reboot is necessary. If you know what your last package is, you can check that but a chainer normally handles eating the reboot requests (error code 3010, ERROR_SUCCESS_REBOOT_REQUIRED).
Note that the property is only set by MSI. If another installer (CBS, etc.) requires a reboot there are different ways of determing that. Alas, there's no single good way to detect if a reboot is pending / required. On Tue, Dec 15, 2009 at 3:30 AM, Mathumathi <[email protected]> wrote: > Hi All, > > During installation of the same package version or a higher version,we need > to find whether there was some pending reboot for the last > uinstallation(lower version package). > > Is that possible with MsiSystemRebootPending for different package > versions? > > > > Regards, > Mathumathi. > > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > > _______________________________________________ > WiX-devs mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wix-devs > > -- Heath Stewart Deployment Technologies Team, Microsoft http://blogs.msdn.com/heaths
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
