Hello WiX community, This question is of "what's the best practice" type. :)
According to SDK, if Windows Installer tries to remove a file in use, which is not EXE, doesn't have a window with title (and a couple of more conditions), it just sets the ReplacedInUseFiles property to 1, and hence will show a dialog "You must reboot your system... " at the end. For instance, an SQLite database locked by aspnet_wp perfectly fits this case... On the other hand, WinLogo specs have a requirement that installation program must not require reboot. Obviously, the above case doesn't satisfy this requirement. So, what's the compromise? Is it a good practice to suppress reboot setting the REBOOT property? What's the best practice working with "reboot mechanism" in general? Thank you! -- Yan ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
