Hi,

 

I am trying to install a dll and its companion pdb file.

 

Below is a merge module which installs a dll and its companion xml and pdb file:

 

<?xml version="1.0" encoding="utf-8"?>

<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";>

  <Module Id="TestDllModule" Language="1033" Version="8.0.0.0">

    <Package Id="24A97400-76DC-4328-8534-8A3E030C194D" Manufacturer="Test A/S" 
InstallerVersion="200" />

    <Directory Id="TARGETDIR" Name="SourceDir">

      <Directory Id="MergeRedirectFolder">

        <Component Id="TestDllComponent" Guid=" 
A727EC59-910E-4231-A418-266FA5C6EF36 ">

          <File Source="Some.dll" KeyPath="yes" />

          <File Id="TestDll" Source="$(var.TestDll.TargetPath)" KeyPath="no" />

          <File Source="$(var.TestDll.TargetDir)$(var.TestDll.TargetName).xml" 
/>

          <File Source="$(var.TestDll.TargetDir)$(var.TestDll.TargetName).pdb" 
CompanionFile="TestDll" />

        </Component>

      </Directory>

    </Directory>

  </Module>

</Wix>

 

Creating an RTM this will work with or without the companionfile attribute.

 

However making an update to the installer elsewhere will trigger a rebuilt of 
the dll (still having the same version number as nothing has changed) and a new 
pbd are created.

 

Now creating a msp between the RTM and the new msi will trigger that the pdb 
file are updated even though the dll aren't updated (with or without the 
companionfile attribute and default REINSTALLMODE). 

 

 

The question is how to ensure that the pdb file only are updated when the dll 
are updated when installing a Patch when using default REINSTALLMODE . 

 

(REINSTALLMODE = emus would work as all dll would be updated as well but we do 
not like updating dll's that haven't changed).

 

 

 

Regards

 

Per

------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to