Swandog wrote: > After installation completes, there was no reboot prompt. The DLL was > replaced. I was unable to reproduce the issue where the COM DLL was not > replaced but what is worse, it's not clear why there was no reboot prompt and > how the MSI was able to replace the DLL while it was held in use. Am I > missing something? Is there any information about how Windows Installer > replaces COM DLLs that are in use? >
MSI doesn't force a reboot to clean up its RBF files. If it was able to "swap out" files by moving the in-use file to the Config.Msi directory and laying down the new file, it won't require a reboot. The MSI SDK has some more details. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
