Verbose log file will probably tell the most. On Sat, Aug 7, 2010 at 7:47 PM, Lucius Fleuchaus <luci...@microsoft.com>wrote:
> The shared library uses the File element without the KeyPath attribute. > > <File Id="CommonLibraryAssembly" DiskId="1" Name="Common.dll" > Source="$(var.TARGETDIR)\Common.dll"/> > > > -----Original Message----- > From: Blair [mailto:os...@live.com] > Sent: Saturday, August 07, 2010 7:01 PM > To: 'General discussion for Windows Installer XML toolset.' > Subject: Re: [WiX-users] Component reference counting & DLL sharing > > Is that shared DLL the keypath of its own component? Do any two files share > any component? > > >From the log, what are the values of REINSTALLMODE and the indications > during costing of the component's state and action? > > -----Original Message----- > From: Lucius Fleuchaus [mailto:luci...@microsoft.com] > Sent: Saturday, August 07, 2010 1:57 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Component reference counting & DLL sharing > > Yes and yes. In addition the shared DLL and all service executables are in > the same directory as well. > ________________________________________ > From: Blair [os...@live.com] > Sent: Saturday, August 07, 2010 1:33 PM > To: 'General discussion for Windows Installer XML toolset.' > Subject: Re: [WiX-users] Component reference counting & DLL sharing > > The file is identical, including every bit in the version resource (all > four parts of the version number, etc.)? > > The file is placed in the exact same directory? > > -----Original Message----- > From: Lucius Fleuchaus [mailto:luci...@microsoft.com] > Sent: Saturday, August 07, 2010 12:11 PM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Component reference counting & DLL sharing > > 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 > > > > ---------------------------------------------------------------------------- > -- > 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 > > > > ---------------------------------------------------------------------------- > -- > 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 > > > > ------------------------------------------------------------------------------ > 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 > > > > ------------------------------------------------------------------------------ > 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 > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users