Hi, I have created some WiX based installers for some services and a web application I am working on at work. We use the installers as part of our test rigs, so we patch our test changes, build the new version and install it. Since this whole process is automated if the MSI determines it needs to reboot, it will.
Previously when I installed the services it would cause a reboot, I assume due to file locks even though the installer would stop the service. My resolution was to stop the service before performing the upgrade, this seems to have solved that issue, although it seems unnecessary. I am now getting the same problem with the Web Application. It automatically deploys a new test build 2 times during the day, once in early morning before anyone is here and once at lunch. The morning build runs fine (I would guess this is because no ones use the application for hours so IIS has released its file locks) but the afternoon builds during lunch forces a reboot most of the time (I would guess because IIS has file locks due to recent activity), which is not only annoying because its rebooting the server, but also the server hosts other software (such as virtual servers) taking that down. I have tried stopping IIS before it begins the install but it still causes a reboot most of the time. Is there a switch that could solve this or some way to make windows locking more sane or something? I am just stumped. Thanks in advance, Adam. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
