We have the following "file-in-use" problem. Five Windows Services are installed on a machine. All services use a shared DLL. All services have their own MSI.
The shared DLL is authored in its own WIX fragment, which is #included in the five service WIX files, hence the shared DLLs ComponentId is shared across all five service MSIs. The first MSI is installed and the windows service starts up referencing the shared DLL. When installing the second service a reboot is required because of a "file in use" error due to the shared DLL which is locked by the first windows service which has already started up. Since the ComponentId is shared, my expectation is that the installer should merely increment the shared component's reference count, as opposed to attempting to copy the shared DLL and thereby preventing the file-in-use error. What should I look at to find the root cause of the file-in-use problem? Thank you. ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
